Re: Who can give me help on the issue 'Guest has not initialized the display (yet).'

[梁朝军]

Hi All,

I trigger a kernel core on host  when issue occur and look the CPU 0 KVM process backtrace like below.

Who know what lead it run in so high CPU usage? I’m not sure it is caused by guest bios load failed.

Is this issue related with any bios.bin?  

Thanks!

在 2021年7月1日，下午2:20，梁朝军 <jesonliang040705@hotmail.com> 写道：

Hi Guys,

Who can give me a help? 

I recently hit the issue that VM can’t boot correctly and show black screen as 'Guest has not initialized the display (yet)’  as below picture

Qemu version in our system is 5.1 and host os is rehat 7.4. kernel version is 3.10.0-693.el7.x86_64.  

/usr/bin/qemu-system-x86_64 -name guest=testvm-aer9umfk,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-testvm-aer9umfk/master-key.aes -machine pc-i440fx-5.1,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -m 4096 -mem-prealloc -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 948e807e-51fc-495d-9808-9496185ace92 -smbios type=0,vendor=phegda -smbios type=1,manufacturer=phegda.com,product=hippo -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-testvm-aer9umfk/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x3 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=/dev/disk/by-id/pbdx-vol-31cbb3dc-da0f-11eb-a280-525400a98761,format=raw,if=none,id=drive-scsi0-0-0-0,cache=writethrough,werror=report,rerror=report -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -drive file=/dev/disk/by-id/pbdx-vol-c6cc745b-e40e-4465-93eb-3ba265606ac0,format=raw,if=none,id=drive-scsi0-0-0-1,cache=none,werror=report,rerror=report -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi0-0-0-1,id=scsi0-0-0-1 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=e6:8e:e2:7e:c1:f6,bus=pci.0,addr=0x8 -netdev tap,fd=31,id=hostnet1,vhost=on,vhostfd=32 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=e6:8e:0a:67:aa:1c,bus=pci.0,addr=0x9 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/hippo/channel/948e807e-51fc-495d-9808-9496185ace92.channel,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=cn.com.pbdata.hippo.0 -vnc 0.0.0.0:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on

That is confuse me for long time. What the potential issue are? Any comments are appreciated.

<PastedGraphic-2.tiff>

Qemu threads:

 535680 root      20   0 4800152 4.044g  11556 R 79.0  4.3  61:18.03 CPU 0/KVM

 535649 root      20   0 4800152 4.044g  11556 S  0.0  4.3   0:00.21 qemu-system-x86

 535673 root      20   0 4800152 4.044g  11556 S  0.0  4.3   0:00.00 qemu-system-x86

 535677 root      20   0 4800152 4.044g  11556 S  0.0  4.3   0:00.00 IO mon_iothread

 535681 root      20   0 4800152 4.044g  11556 S  0.0  4.3   0:00.00 CPU 1/KVM

 535684 root      20   0 4800152 4.044g  11556 S  0.0  4.3   0:00.00 vnc_worker

Thanks!