Proxmox: After Migrating VMs to node1, All VM Consoles Broke (“Failed to run vncproxy”) — Full Diagnosis and Fix LogThis post documents the full troubleshooting process (what I checked and why), not just the final workaround. Environment There is a dedicated 10G internal network between the cluster nodes and the NAS: node1: 172.16.0.20 node2: 172.16.0.21 NAS2 (Synology): 172.16.0.10 The NAS also has another reachable service IP: NAS2 service IP: 192.168.10.132 0. Symptoms After migrating VMs from node2 to node1: No VM console could be opened in the Proxmox Web UI. The UI error was: failed to run vnc proxy Additional observations: The node-level shell console (node1 → Shell) still worked. Running qm vncproxy <vmid> manually on node1 returned: LC_PVE_TICKET... To read more, click here
Migrating an IBM Windows Server 2003 Physical Machine to Proxmox and Reducing Disk SizeThis post documents the complete process of converting an old IBM physical server running Windows Server 2003 into a virtual machine on Proxmox VE, and then shrinking its 2 TB system disk down to a much smaller, space-efficient image. 1. P2V with VMware vCenter Converter (XP-Compatible Version) Because the original system still ran within the Windows XP–era software environment, I used an older release of VMware vCenter Converter (P2V Virtual Machine Converter) — one of the few versions that still runs correctly on XP / Server 2003. Steps Install VMware vCenter Converter on the IBM host. Choose Convert Local Machine.... To read more, click here
