Proxmox 6.2 VE - change on cpu results in " failed to run vncproxy"

May 16, 2020
271
16
38
51
Antwerp, Belgium
commandline.be
Dear,

After (re)install Proxmox works as expected. There are issue however which i fail to work around.

* When i create a VM and i alter the CPU from the default kvm64 to anything else (host or qemu64) this results in " failed to run vncproxy", i find now way to recover from this.

EDIT: wrong, i managed to recover from it, by erasing the CPU setting.

* when an iso is named like filename.something.iso proxmox fails to boot from it
 
Last edited:
hi,

* When i create a VM and i alter the CPU from the default kvm64 to anything else (host or qemu64) this results in " failed to run vncproxy", i find now way to recover from this.

can't reproduce it here with multiple vms running different cpu architectures. does it not work after you get the error? can you post the config of such VM? (qm config VMID)

* when an iso is named like filename.something.iso proxmox fails to boot from it
can't reproduce this either... did you modify the boot order in the options?
 
The "failed to run vncproxy" is for now mitigated by resetting value for host to blank, having work with qemu on CLI i think this is not really how i expect QEMU to behave. I do not understand why proxmox has problems with the value changing from blank > kvm64 > qemu64 > host or any other.

Just checked, the boot order is correct, the ISO simply does not boot with proxmox. or virtualbox. I will have to checksum that iso to see if it is not damaged.
 
Last edited:
* what is the output of pveversion -v ?

The "failed to run vncproxy" is for now mitigated by resetting value for host to blank, having work with qemu on CLI i think this is not really how i expect QEMU to behave. I do not understand why proxmox has problems with the value changing from blank > kvm64 > qemu64 > host or any other.
please post your VM configuration...

Just checked, the boot order is correct, the ISO simply does not boot with proxmox.
it works here with the latest version. even if there are multiple "." characters in the name it boots correctly. if it's an ISO file the boot order should show CD-ROM
 
  • Like
Reactions: Joris L.
Thanks. Currenlty considering a PEBKAC issue for the QRadarCE7_3_0.GA.iso, it does not boot in virtualbox either.

For the CPU, i'm not sure how to understand what i see. It is undeniable changing the CPU at any given time makes the VM unbootable.

I am Proxmox VE 6.2 with most recent updates installed.