Guest has not initialized the display (yet)

TwiX

TwiX

Renowned Member
Feb 3, 2015
320
23
83
Hi,

4 HA Vms were not able to reboot properly this morning at 4:30 pm (reboot via cron).
These vms are running Centos 7 64 bits with qemu-guest-agent (hosted by different nodes).

Seems that my 3 nodes cluster is up to date :

Code: 
proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.13.4-1-pve: 4.13.4-25
pve-kernel-4.10.17-4-pve: 4.10.17-24
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90
ceph: 12.2.1-pve3

When I tried to connect to the vm console, it shows "Guest has not initialized the display (yet)". VMs vCPUs were almost at 100 %.

So I tried to reset these VMs without any effect.
I also try to stop the VMs but it took more than 10 min to succeed (shutdown and no 'stop' as I required). I guess it tried to shutdown vm via qemu-guest agent but services were not started indeed. After a while proxmox shutdown vm with SIGTERM terminating as you can see :

Code: 
task started by HA resource agent
VM quit/powerdown failed - terminating now with SIGTERM
TASK OK

Do you if it's a known bug ?

Thanks in advanced !
 
"Guest has not initialized the display yes" is an very early boot error of the VMs and can have a number of different cause.
As it happens very early during the boot sequence it is usually not possible to do a proper shutdown, either via ACPI or guest-agent.

Did the machines started after they were stopped with:
task started by HA resource agent
VM quit/powerdown failed - terminating now with SIGTERM
TASK OK

?
 
Hello

Yes, all stopped vms via HA this morning are now 'up and running'
 
Hello,

It happened again this morning, for a debian 8 64 bits with qemu-guest-agent installed.
The VM tried to reboot @ 4:30 am (via a simple cron 'shutdown - r now')

The screen of the vm console was totally black.

As usual, the shutdown of the VM took more than 10 min.

Nothing special mentioned on hypervior syslog :(
 
Hi,

Unfortunately, It occurred again...
Don't you think it could be possible that a KVM bug affecting the whole cluster when more than 2-3 vms are rebooting at the same time ?
 
Hi all, I noticed this problem after a backup (mode STOP).
The guest is a windows 2016 and is using virtio-SCSI.
In the past there has been problem with backup using STOP mode and VIRTIO.
I suspect there may be problem with virtio-SCSI as well.
Did you notice if the message appeared after a scheduled backup?
If yes, what modality of backup did you use?
 
I tried to do a backup with SNAPHOST mode and the guest started fine.
I forgot to mention that the guest was not running during backup.
I'm groin to try once more to backup with STOP mode and see it replicates again.
 
Well, I wrote to early.
This time the guest was able to boot but it ended with a blue screen!

upload_2017-11-16_15-33-26.png

This is my guest conf

Code: 
agent: 1
balloon: 2048
boot: cdn
bootdisk: scsi0
cores: 12
cpu: host
ide2: iso:iso/sql206_standard_ats.iso,media=cdrom,size=2893164K
memory: 12288
name: win2016
net0: virtio=2A:E4:7B:F8:3F:F3,bridge=vmbr0
numa: 0
ostype: win10
scsi0: sas:vm-102-disk-1,cache=writeback,discard=on,size=101G
scsi1: sata:vm-102-disk-1,backup=0,cache=writeback,size=20G
scsi2: sata:vm-102-disk-2,cache=writeback,discard=on,size=200G
scsihw: virtio-scsi-pci
smbios1: uuid=2c644a01-2e9e-4777-8623-f6b78ce5bece
sockets: 1
 
I also forgot to mentions that the guest ha no problem restarting after it has been shut down by qem-guest-agent (right click, shutdown).
 
Hi all,

All my backups are made via SNAPSHOT mode.
It only occurs when vms try to reboot OS, eg on linux vms via cron '/sbin/shutdown -r now ' @ 4:30 am. Snapshots backups are already done (until 3:00 am).
 
Hi,

It still happens sometimes on several nodes of 2 distinct clusters in my case.
 
TwiX said:
Hi,

It still happens sometimes on several nodes of 2 distinct clusters in my case.
Click to expand...

You run latest kernel? Please post your:

> pveversion -v
 
You must log in or register to reply here.
Top Bottom