[SOLVED] Proxmox 7.0-13 Console issue with Windows Guests (Guest has not initialized the display (yet))

[Abrucci]

Hey there,

i have freshly installed Proxmox 7.0-13 (Debian 11) on a dedicated Server with AMD Ryzen 7 3700x (8 x 3,9 GHz).
Installed via. Debian 11 and Repositorys (not with Installation ISO).

Creating and working with Linux VMs works without any problems.
Now i'm trying to create Windows VMs. After boot and changing to Console Tab it only shows "Guest has not initialized the display (yet)".

When going back to Proxmox 6 (Debian 10) everything works fine but i need Proxmox 7 to use nested Virtualization with AMD CPU...
Any Ideas what the problem can be?

 

[dcsapak]

if you chose uefi + default machine type (i440fx) this is currently a bug. for now you could either set q35 as a machine type, or use the 'old' uefi image type (without secure boot)
for that you'd have to remove the efidisk and create one on the cli with:

qm set ID -efidisk0 <YOUR-STORAGE>:1

 

[Abrucci]

if you chose uefi + default machine type (i440fx) this is currently a bug. for now you could either set q35 as a machine type, or use the 'old' uefi image type (without secure boot)
for that you'd have to remove the efidisk and create one on the cli with:

qm set ID -efidisk0 <YOUR-STORAGE>:1

Thank you for the reply.
Are there any limitations in using q35?

 

[Abrucci]

After changing the efi disk with the command above, the console works for a few seconds. After that i got the error


Task viewer: VM/CT 1000 - Console

OutputStatus

Stop
VM 1000 qmp command 'set_password' failed - unable to connect to VM 1000 qmp socket - timeout after 31 retries

*EDIT: q35 does the trick here

 

[dcsapak]

Are there any limitations in using q35?

you can only use ide0 and ide2 (ide1/3 will not work) but aside from that, i am not aware of any limiations
there are a few differences though (pcie bus, audio/usb controller, etc) but those should not matter in most cases

After changing the efi disk with the command above, the console works for a few seconds. After that i got the error


Task viewer: VM/CT 1000 - Console

OutputStatus

Stop
VM 1000 qmp command 'set_password' failed - unable to connect to VM 1000 qmp socket - timeout after 31 retries

that looks like an unrelated problem... is the vm still running?

 

[Abrucci]

you can only use ide0 and ide2 (ide1/3 will not work) but aside from that, i am not aware of any limiations
there are a few differences though (pcie bus, audio/usb controller, etc) but those should not matter in most cases


that looks like an unrelated problem... is the vm still running?

Well, i can't ping it as it's still in the Windows Installer. But it says "started".
Combination was i440fx-6.0 with efi disk without secure boot.

The problem seems to occur when 2 VMs with this configuration are running.
However changing from i440fx to q35 solved both problems.