Guest has not initialized display

[ZeusTheGreekGod]

Server is an Epyc 7401P based VM
proxmox installed fine and i can run containers
but after trying multiple display options
i cannot get display for a Ubuntu 22.04 liver server
Can someone suggest something else to try

cheers

 

[ZeusTheGreekGod]

I have googled and cannot get anywhere ..anyone willing to help figure out the issue ?

 

[fiona]

Hi,
please share the VM configuration qm config <ID> (replacing <ID> with the actual ID) and the output of pveversion -v. Does this happen before or after installation? Is there anything in the host's system logs/journal or in the VM <ID> - Start task (lower section in the UI, double click to get the log)?

 

[ZeusTheGreekGod]

Thanks Fiona .. i had deleted all VM and did a fresh install
agent: 1
boot: order=scsi0;ide2;net0
cores: 2
cpu: x86-64-v2-AES
ide2: local:iso/ubuntu-22.10-live-server-amd64.iso,media=cdrom,size=1604132K
memory: 3048
meta: creation-qemu=8.0.2,ctime=1699355678
name: VM100
net0: virtio=FA:0B:B52:3B:CA,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local:100/vm-100-disk-0.qcow2,discard=on,iothread=1,size=32G
scsihw: virtio-scsi-single
smbios1: uuid=3f0963e7-65f2-4cf8-9bf7-067a90e3d33d
sockets: 1
vmgenid: 1673db77-afec-4918-9cf0-8a1ff9ca02a8

------------------------------------------
proxmox-ve: 8.0.1 (running kernel: 6.2.16-3-pve)
pve-manager: 8.0.3 (running version: 8.0.3/bbf3993334bfa916)
pve-kernel-6.2: 8.0.2
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx2
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-3
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.0
libpve-access-control: 8.0.3
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.5
libpve-guest-common-perl: 5.0.3
libpve-http-server-perl: 5.0.3
libpve-rs-perl: 0.8.3
libpve-storage-perl: 8.0.1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 2.99.0-1
proxmox-backup-file-restore: 2.99.0-1
proxmox-kernel-helper: 8.0.2
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.0.5
pve-cluster: 8.0.1
pve-container: 5.0.3
pve-docs: 8.0.3
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.2
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.4
pve-qemu-kvm: 8.0.2-3
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1

 

[ZeusTheGreekGod]

TASK ERROR: connection timed out

in the logs on the dashboard

 

[fiona]

TASK ERROR: connection timed out

in the logs on the dashboard

Is this the Start task or the Console task?

Can you also share the system logs/journal? Those might contain more information about the issue. Does ps -e -o stat,command | grep '^D' produce any output?

 

[ZeusTheGreekGod]

1. start command
2. no output of the ps command you gave.

 

[ZeusTheGreekGod]

is there a logfile i can check ..nothing in /var/log/pve/index beside VM exited with code 1

 

[ZeusTheGreekGod]

rotated logs, and started vm again
logs
ov 08 22:08:31 hostbrr pvedaemon[825]: <root@pam> end task UPID:hostbrr:0000207C:00047898:654B500D:qmstart:100:root@pam: OK
Nov 08 22:08:32 hostbrr pvedaemon[825]: <root@pam> starting task UPID:hostbrr:000020DB:000479B6:654B5010:vncproxy:100:root@pam:
Nov 08 22:08:32 hostbrr pvedaemon[8411]: starting vnc proxy UPID:hostbrr:000020DB:000479B6:654B5010:vncproxy:100:root@pam:
Nov 08 22:08:32 hostbrr pvedaemon[824]: <root@pam> starting task UPID:hostbrr:000020DD:00047A0E:654B5010:vncproxy:100:root@pam:
Nov 08 22:08:32 hostbrr pvedaemon[8413]: starting vnc proxy UPID:hostbrr:000020DD:00047A0E:654B5010:vncproxy:100:root@pam:
Nov 08 22:08:42 hostbrr pvedaemon[8411]: connection timed out
Nov 08 22:08:42 hostbrr pvedaemon[825]: <root@pam> end task UPID:hostbrr:000020DB:000479B6:654B5010:vncproxy:100:root@pam: connection timed out

 

[ZeusTheGreekGod]

disregard previous message figured out that issue ..while all this installing/reinstalling i didnt add the proper hostname so certs were failing
now certs are updated correctly and pvestatd is running
but still same issue ..Guest hasnt started display


Nov 08 22:52:44 pve.domaincom pvedaemon[2751]: starting vnc proxy UPIDve:00000ABF:00014F19:654B5A6C:vncproxy:101:root@pam:

 

[fiona]

You can use e.g. journactl -b to see the system logs for the current boot. Press G to scroll to the end.

 

[ZeusTheGreekGod]

nothing jumps out in the logs

-----------
pvedaemon[805]: <root@pam> starting task UPIDve:00001F5E:0004C282:654B6341:qmstart:101:root@pam:
pvedaemon[8030]: start VM 101: UPIDve:00001F5E:0004C282:654B6341:qmstart:101:root@pam:
systemd[1]: Started 101.scope.
kernel: device tap101i0 entered promiscuous mode
kernel: vmbr0: port 1(fwpr101p0) entered blocking state
kernel: vmbr0: port 1(fwpr101p0) entered disabled state
kernel: device fwpr101p0 entered promiscuous mode
kernel: vmbr0: port 1(fwpr101p0) entered blocking state
kernel: vmbr0: port 1(fwpr101p0) entered forwarding state
kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
kernel: device fwln101i0 entered promiscuous mode
kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
kernel: fwbr101i0: port 1(fwln101i0) entered forwarding state
kernel: fwbr101i0: port 2(tap101i0) entered blocking state
kernel: fwbr101i0: port 2(tap101i0) entered disabled state
kernel: fwbr101i0: port 2(tap101i0) entered blocking state
kernel: fwbr101i0: port 2(tap101i0) entered forwarding state
pvedaemon[805]: <root@pam> end task UPIDve:00001F5E:0004C282:654B6341:qmstart:101:root@pam: OK
pvedaemon[804]: <root@pam> starting task UPIDve:00001FA7:0004C3DF:654B6345:vncproxy:101:root@pam:
pvedaemon[8103]: starting vnc proxy UPIDve:00001FA7:0004C3DF:654B6345:vncproxy:101:root@pam:

 

[ZeusTheGreekGod]

Attaching boot log

 

[ZeusTheGreekGod]

anyone else have an idea what might be going on ?
its a AMD EPYC server

cheers

 

[wigor]

We have same "Guest has not initialized display ..." if we set "freeze CPU at startup".
Even freeze=1 does not show up in your qm config, maybe you have a problem with the cpu-type of the VM.
Did you try "host" already?

 

[fiona]

Hi,

We have same "Guest has not initialized display ..." if we set ""reeze CPU at startup".

yes, that's expected. You need to manually resume the guest after startup if you use that setting.

@ZeusTheGreekGod Does the same issue happen with other ISOs/distros? Is this when trying to boot via ISO or after installation of Ubuntu?

 

[ZeusTheGreekGod]

i dont think so i hard run debian after this didnt work but that ran into other issues
so i just installed minimal on it and it seems to be running ..issue was with graphics and i am guessing ( not sure) has something to do with kvm
incidentally i saw that same message for a second while installing sosumi ( a macos installer for ubuntu ) yesterday while doing a macos install ( on my ryzen laptop ).
just for a second then display worked

cheers