Jump to content
keepitshut

Guest has not initialised the display (yet)

10 posts in this topic Last Reply

Recommended Posts

Hi everyone, I have been trying to setup a Ubuntu server install as a VM. After creating the VM and launching the browser VNC, all I get is a black screen with "Guest has not initialised the display (yet)".  HVM is enabled, but my hardware does not support IOMMU. Any idea whats causing this?

 

Using Unraid 6.4.1 and Ubuntu Server 16.04

 

Thank you!

Screen Shot 2018-03-04 at 3.39.00 AM.png

Share this post


Link to post
2018-03-03 19:41:49.812+0000: starting up libvirt version: 3.8.0, qemu version: 2.10.2, hostname: jx
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=Ubuntu,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-6-Ubuntu/master-key.aes -machine pc-q35-2.10,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/a054925e-26c0-f812-dbd9-8d677594237f_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 2560 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid a054925e-26c0-f812-dbd9-8d677594237f -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-6-Ubuntu/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 pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunata0-0-0,id=sata0-0-0,bootindex=2 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:54:19:45,bus=pci.1,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-6-Ubuntu/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0,websocket=5700,password -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 -msg timestamp=on
2018-03-03 19:41:49.812+0000: Domain id=6 is tainted: high-privileges
2018-03-03 19:41:49.812+0000: Domain id=6 is tainted: host-cpu
2018-03-03T19:41:49.869747Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)

These are the logs. I don't see anything out of the ordinary though

Share this post


Link to post

Hey @keepitshut 

 

I'm seeing the same problem with an ubuntu desktop 17.10 VM. I've managed to create and destroy more than a couple of ubuntu VMs with the same install iso and small variations in settings (disk / ram size) during last week or two, but today I'm trying to create one, all the same settings that worked before and keep getting the same error as you...

 

2018-03-11 15:45:19.209+0000: starting up libvirt version: 3.8.0, qemu version: 2.10.2, hostname: BLABLABLA
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=Blabla,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-9-Blabla/master-key.aes -machine pc-q35-2.10,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 2560 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-9-Blabla/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 pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=-0,id=sata0-0-0,bootindex=2 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=30 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=xx:xx:xx:xx:xx:xx,bus=pci.1,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-9-Blabla/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0,websocket=5700 -k hr -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 -msg timestamp=on
2018-03-11 15:45:19.209+0000: Domain id=9 is tainted: high-privileges
2018-03-11 15:45:19.209+0000: Domain id=9 is tainted: host-cpu
2018-03-11T15:45:19.260508Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/1 (label charserial0)

Did you manage to find out anything useful about our shared problem? Please share.

 

EDIT: A restart was all it took. Seems I've gone all fussy way too early.

EDIT2: Seems I celebrated too early. After a VM restart  I can login and then - blank screen. Error in log: 

((null):25009): SpiceWorker-Warning **: red_worker.c:163:rendering_incorrect: rendering incorrect from now on: get_drawable

EDIT3: Looks like changing the clients resolution causes the rendering incorrect thingy. 

Edited by sinbrkatetete
RESTART

Share this post


Link to post

ive tried all of the above and am still having the problem. this occurred to me after trying to pass through a GTX 770, not getting anywhere and setting it back to VNC. now no VMs can start.

 

EDIT: creating a new VM and attaching the old disk fixed the problem. Not sure how much damage that does though. Try configuring 2 graphics displays in the VM config: VNC and the GPU

Edited by isaacery

Share this post


Link to post

Did you ever figure this out? I am trying to access the VM through VNC but still attach a graphics card for machine learning. Getting the same error when I manually edit the XML.

Share this post


Link to post
On 1/24/2019 at 7:48 PM, willemwillem vermeulen said:

i found changing the memory allocation resolved this

Worked for me also. Linux Mint VM, VNC graphics. 
Seemed to not like half gigs of RAM (eg, booted with 4GB and 3GB but not 3.5 or 2.5)

Share this post


Link to post

Hi,

I have the same probs with that. Unraid 6.8.3. All Vm´s that switched from or to GPU Passthrough to VNC back have the problems. I find out that after switching the Grafik output the "bus" from  0x00 chnaged to 0x07. With these settings the vms dosen´t work. After change the bus back to 0x00 the vm works fine. If the bus 0x00 is occupied, change the slot to 2 or 3. Sorry for my bad english :-) <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>

Share this post


Link to post
Posted (edited)
On 4/8/2020 at 5:43 PM, Ghostly2002 said:

Hi,

I have the same probs with that. Unraid 6.8.3. All Vm´s that switched from or to GPU Passthrough to VNC back have the problems. I find out that after switching the Grafik output the "bus" from  0x00 chnaged to 0x07. With these settings the vms dosen´t work. After change the bus back to 0x00 the vm works fine. If the bus 0x00 is occupied, change the slot to 2 or 3. Sorry for my bad english :-) <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>

Worked for me, from the VM template, flip toggle on top right from form to xml and made change,
Thanks

Edited by namtr0
more detail

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.