qemu vnc console can only show "no suitable video mode" on taishan2280 server

[Zhanglei Mao]

Qemu vnc console can only show "no suitable video mode" and nothing else both on opensack dashboard (vnc) or virt-manager. This was tested on Taishan2280 server (D05).

Please see attached screen shoot.

[Zhanglei Mao (zhanglei-mao)]

error screen picture

[Zhanglei Mao (zhanglei-mao)]

qemu error sceen shot via virt-manager

[Zhanglei Mao (zhanglei-mao)]

the out put of "virsh dumpxml"
...
    <graphics type='vnc' port='5900' autoport='yes' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='virtio' heads='1' primary='yes'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    </video>
...

This should be OpenStack configured for VNC and qemu devices. If I manual remove them, and the virt-manager can become normally which show grub menu, boot message and login etc.

[Zhanglei Mao (zhanglei-mao)]

The commend link for qemu which created by nova compute, the vcn parameter are:
-vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.5,addr=0x0

ubuntu@hc3:~$ ps auxww |grep -i qemu
libvirt+ 1157628 3.6 0.1 5691124 737996 ? Sl 04:34 1:21 qemu-system-aarch64 -enable-kvm -name guest=instance-0000004f,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-20-instance-0000004f/master-key.aes -machine virt-2.11,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 -cpu host -drive file=/usr/share/AAVMF/AAVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/var/lib/libvirt/qemu/nvram/instance-0000004f_VARS.fd,if=pflash,format=raw,unit=1 -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid da45ffb1-9501-443a-97e2-f1293fbfd08f -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-20-instance-0000004f/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-shutdown -boot strict=on -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 -device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 -device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 -device pcie-root-port,port=0xb,chassis=4,id=pci.4,bus=pcie.0,addr=0x1.0x3 -device pcie-root-port,port=0xc,chassis=5,id=pci.5,bus=pcie.0,addr=0x1.0x4 -device pcie-root-port,port=0xd,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x5 -device qemu-xhci,id=usb,bus=pci.2,addr=0x0 -object secret,id=virtio-disk0-secret0,data=Z3QA44y9KQVjm1An9Z7JiVegjxUJjdHPo8fjGseVK3E=,keyid=masterKey0,iv=Ysbjc+1zq7/PnAMK2/WjJA==,format=base64 -drive file=rbd:cinder-ceph/volume-ece667dd-5d26-40cd-b27e-64be5803968e:id=cinder-ceph:auth_supported=cephx\;none:mon_host=172.16.25.47\:6789\;172.16.25.54\:6789\;172.16.25.60\:6789,file.password-secret=virtio-disk0-secret0,format=raw,if=none,id=drive-virtio-disk0,serial=ece667dd-5d26-40cd-b27e-64be5803968e,cache=none,discard=unmap -device virtio-blk-pci,scsi=off,bus=pci.3,addr=0x0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,host_mtu=1500,netdev=hostnet0,id=net0,mac=fa:16:3e:85:cc:99,bus=pci.1,addr=0x0 -add-fd set=2,fd=30 -chardev pty,id=charserial0,logfile=/dev/fdset/2,logappend=on -serial chardev:charserial0 -device usb-tablet,id=input0,bus=usb.0,port=1 -device usb-kbd,id=input1,bus=usb.0,port=2 -vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.5,addr=0x0 -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 -msg timestamp=on

[Zhanglei Mao (zhanglei-mao)]

From the arm qemu wiki:
https://wiki.qemu.org/Documentation/Platforms/ARM
vns seems works and require as:

virt machine graphics

Graphics is also available, but unlike x86 there is no default display device enabled: you should select on from the Display devices section of "-device ?". One good option is to use:

-device virtio-gpu-pci
and enable the following Linux kernel options:

CONFIG_DRM=y
CONFIG_DRM_VIRTIO_GPU=y
Also, for some reason, the SDL graphic window does not open under certain circumstances as of v2.12, so you might need to use another method such as VNC:

-vnc :0
and then connect to it with:
vinagre :5900

[Zhanglei Mao (zhanglei-mao)]

For 18.04.2 ga-kernel of Linux hc3 4.15.0-47-generic, the CONFIG_DRM=y and CONFIG_DRM_VIRTIO_GPU=y seems already set. Test with drm virtio-gpu modules load, it seems same. I tested by delete instance via dashboard and create it again on the same hc3.maas host.

For the virt-manager still display for "error: no suitable video mode found". But the openstack dashboard can display nothing.

[Zhanglei Mao (zhanglei-mao)]

After add this to /etc/default/grub,
ubuntu@test-2:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=0ba22f57-08ab-4b84-9592-936a48bd5692 ro console=tty0 quiet splash vt.handoff=1
ubuntu@test-2:~$

The issues is same which still show as "error: no suitalbe video mode found"

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1877083/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]