windows 11 - guest has not initialized the display (yet)

R

requests

New Member
Nov 15, 2020
17
1
3
40
Hello

I'm trying to create a windows 11 VM in proxmox VE 7, but once i start the vm it says "guest has not initialized the display (yet)"
1634582469619.png
packages & version installed
proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve)
pve-manager: 7.0-13 (running version: 7.0-13/7aa7e488)
pve-kernel-helper: 7.1-2
pve-kernel-5.11: 7.0-8
pve-kernel-5.4: 6.4-6
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.4.140-1-pve: 5.4.140-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-10
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.11-1
proxmox-backup-file-restore: 2.0.11-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-4
pve-firmware: 3.3-2
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-16
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1
 
Last edited:
Hi,
there is a known issue when the machine type is i440fx (fix is in the works), but it should work when the type is q35. Could you please post the full configuration qm config <ID>. Has the VM been newly created or was it in use before?
 
Fabian_E said:
Hi,
there is a known issue when the machine type is i440fx (fix is in the works), but it should work when the type is q35. Could you please post the full configuration qm config <ID>. Has the VM been newly created or was it in use before?
Click to expand...
bios: ovmf
boot: order=virtio0;ide2;net0
cores: 8
efidisk0: local:107/vm-107-disk-1.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
ide2: local:iso/Win11_English_x64.iso,media=cdrom,size=5369126K
machine: pc-q35-5.2
memory: 8192
name: win-test
net0: virtio=5E:69:24:DB:2C:0B,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-single
smbios1: uuid=8b37fa25-e171-48d2-971c-6fbb326fd1e3
sockets: 1
tpmstate0: local:107/vm-107-disk-2.raw,size=4M,version=v2.0
virtio0: local:107/vm-107-disk-0.qcow2,iothread=1,size=64G
vmgenid: 6588926d-a6e7-4b42-b300-cbedcb79c7a5

the vm is newly created
 
I'm not able to reproduce the issue here as long as the machine type is not i440fx. Could you check the integrity of the OVMF files with
Code: 
debsums -s pve-edk2-firmware
(you might need to install debsums first)? If there is no output, please try re-creating the VM again.

If it still doesn't work, please post more information about your host.
 
You must log in or register to reply here.
Top Bottom