Guest has not initialized display (yet)

[hitorai]

Hello everyone.

Last week I updated my cluster of 4 nodes from Proxmox v5 to v6. The problem I'm confronted is, that now my vms in our nested Proxmox environment does not work anymore. Everytime I try to boot a VM in my nested proxmox I always get this message in the console:

Guest has not initialized display (yet)

I tried it on a nested proxmox v6 and v5 and installed them both fresh to test them. The vms always show the same message and the CPU usage is at 100%
I tried it with Windows-, Debian- and CentOS vms

Container on the other hand seem to work without problem.

Regards
hitorai

 

[t.lamprecht]

I tried it on a nested proxmox v6 and v5 and installed them both fresh to test them. The vms always show the same message and the CPU usage is at 100%
I tried it with Windows-, Debian- and CentOS vms

So it happens now on both PVE 5.x and 6.x in your new tests?

Guest has not initialized display (yet)

Are the VM marked as "paused" in the webinterface? Or better, what does

qm status 102 --verbose | tail -23

outputs?

 

[hitorai]

Edit: There is no system installed, can't load the iso. But is configured for Debian.

This one is on a nested Proxmox 6.0.4 (Debian VM):

root@pve:~# qm status 100 --verbose | tail -23
                rd_merged: 0
                flush_total_time_ns: 0
                rd_bytes: 0
cpus: 2
disk: 0
diskread: 0
diskwrite: 0
maxdisk: 21474836480
maxmem: 1073741824
mem: 37428480
name: DEBIAN
netin: 130
netout: 0
nics:
        tap100i0:
                netin: 130
                netout: 0
pid: 12161
qmpstatus: running
status: running
template:
uptime: 2425
vmid: 100

This one is on a nested Proxmox 5.3-8 (Debian VM):

root@pve:~# qm status 100 --verbose | tail -23
                failed_flush_operations: 0
                wr_merged: 0
                flush_total_time_ns: 0
cpus: 1
disk: 0
diskread: 0
diskwrite: 0
maxdisk: 21474836480
maxmem: 536870912
mem: 11063897
name: DEBIAN
netin: 178
netout: 0
nics:
        tap100i0:
                netin: 178
                netout: 0
pid: 1826
qmpstatus: running
status: running
template:
uptime: 2575
vmid: 100

 

[hitorai]

I played a little with CPU-Flags and BIOS settings but no progress. The same screen always smiles in my face.

 

[hitorai]

We've found a workaround for this problem, but it's not satisfying. We downgraded the Kernel Version to Linux 4.15.18-21-pve. Now if we use the OS-Type: Microsoft WIndows, 10/2016/2019 on the normal Proxmox Environment (not the nested one), the VMs won't start and shows the following errormessage:

Logs
()
Hyper-V IPI send support (requested by 'hv-ipi' cpu flag)  is not supported by kernel
kvm: kvm_init_vcpu failed: Function not implemented
TASK ERROR: start failed: command '/usr/bin/kvm -id 115 -name Test2-Windoof -chardev

CPU which we use on the node is a AMD Opteron(tm)Processor 6136