Fixed, leaving for posterity:
I currently have a 6 node Proxmox system with all current patches. 5 of the nodes, I can console without issue. Any VM on the 6th node hangs at the above attempt. The underlying VMs are still running, as I can connect to server VMs via ssh, etc. I can't connect by VNC though.
So far I've attempted pvecm updatecerts thinking that may have something to do with it. The node in question functions correctly through the web interface excepting for this issue with launching a console. Note this is a console to a VM on the offending host. Migrating that same host to another node allows console connection just fine.
Any ideas? The one difference between this node and the others is this a 48 core 1.8Ghz server, the others are 32 core 3.2Ghz servers. Underlying storage is Ceph Hammer.
Resolution: pve16 (the 6th node, long story) was a recent add. pve10 (the main node) had not had pve16's ssh key accepted. Checked that on a whim, accepted, and was able to connect to a vm's console on pve16.
I currently have a 6 node Proxmox system with all current patches. 5 of the nodes, I can console without issue. Any VM on the 6th node hangs at the above attempt. The underlying VMs are still running, as I can connect to server VMs via ssh, etc. I can't connect by VNC though.
So far I've attempted pvecm updatecerts thinking that may have something to do with it. The node in question functions correctly through the web interface excepting for this issue with launching a console. Note this is a console to a VM on the offending host. Migrating that same host to another node allows console connection just fine.
Any ideas? The one difference between this node and the others is this a 48 core 1.8Ghz server, the others are 32 core 3.2Ghz servers. Underlying storage is Ceph Hammer.
Resolution: pve16 (the 6th node, long story) was a recent add. pve10 (the main node) had not had pve16's ssh key accepted. Checked that on a whim, accepted, and was able to connect to a vm's console on pve16.
Last edited:
