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!

try looking in your vm logs for errors

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

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 March 12, 20188 yr by sinbrkatetete
RESTART

i found changing the memory allocation resolved this

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 August 1, 20196 yr by isaacery

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.

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)

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'/>

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 June 29, 20206 yr by namtr0
more detail

For me the solution earlier mentioned by isaacery was to create a new VM with exact the same configuration as the one which does not work (with the primary vDisk location pointing to the correct old disk). The new VM booted instantly without any problems.

 

My problem started when I changed the Graphic card from VNC to the GPU (and back again as the VM did not start anymore). In VNC I got the message "Guest has not initialized the display (yet)".

Just had this same issue with "guest has not initialized the display (yet)", deleting the VM (keeping the image) and re-creating fixed it.

 

Thanks.

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'/>

 

 

I had the same problem with Macinabox BigSur after removing the graphic card and trying to get back to VNC.

I also had to change the controllers that were on bus='0x00' slot='0x01' to slot='0x02' to fix the problem.

 

Thank you!!!!!

This community is AMAZING!!!!

 

 

 

 

@DrLucasMendes do can you share your XML, I had the exact same problem but can't find my conflict for the life of me

To anyone coming with similar issue- easier way to solve might be to run 

qm cleanup <vmid> False True

 

It was a solution for me

Edited September 21, 20214 yr by newinthis
new info

On 9/21/2021 at 10:59 PM, newinthis said:

To anyone coming with similar issue- easier way to solve might be to run 

qm cleanup <vmid> False True

 

It was a solution for me

Where did you install qm from?

 

Edit: recreating the VM also fixes it, as mentioned above.

Edited October 3, 20214 yr by realies

On 4/9/2020 at 9:43 AM, 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'/>

Perfect, like many had trouble going from GPU passthrough back to VNC, awesome sauce!

 

thank you!

Same scenario... flipped from VNC to a passthrough (which didn't work) and trying to get back to working VNC.

 

Had to rebuild one. Another is a Hackintosh that I'm still trying to repair.

On 2/18/2022 at 10:04 AM, DaMAN said:

Perfect, like many had trouble going from GPU passthrough back to VNC, awesome sauce!

 

thank you!

how and where on the vm are we supposed to do that?

On 8/1/2019 at 7:27 PM, isaacery said:

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

Yes, Having exactly the same issue. All was good and working before I tried to pass through my NVidia Card. VM wouldnt fire up. Edited the VM settings back to VNC and got this message. Seems bricked. Guess I'll have to install WIN11 (Again)....

 

On 4/9/2020 at 7:43 AM, 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'/>

So where are these settings (for noobs like me)??

Thanks in Advance.

Thanks, helped me out too.

Thanks every one...I've had the same problem but ended up just re-creating the VM as it was not playing with me.

 

For any one doing this for a windows machine remember to get your UUID saved first.

 

And for any one wondering where this xlm is just go in to the Vm and go to Form View./XML View

 

Look for <video> and </video> - I found making sure I had only set VNC and then saved, then gone in the view I was able to locate.

 

T

Edited March 16, 20233 yr by ccsnet

@Ghostly2002, your advice is still useful 😊 I managed to fixed an Ubuntu VM. Tried to make an iGPU and during the tests switched over to VNC and then got the "Guest has not initialized..." message. Similarly, the issue lied in the bus being changed to 0x07 and slot to 0x01. Changed the bus to 0x00 and the slot to 0x02 and the VM booted just fine.

Edited September 30, 20232 yr by 5ven

On 4/9/2020 at 12:43 AM, 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'/>

 

This also did it for me after switching from GPU to VNC back and forth. So setting the bus back to 0x00 did it.