Hi all,

 

Very strange issue with my Windows 10 VM (using hardware passthrough for GPU/PCI-e USB3.0 card and soundcard).

 

Every time I boot the VM from cold it hangs at the Windows startup screen (windows logo and swirly-ma-jig). It will then end up in a 'stopped' state. I can then press start it works fine! I can reproduce the issue on demand. This may also be related to an issue I'm having where the VM seems to stall for maybe half a second or so during general use. Most noticeable when watching youtube - this manifests itself in very brief distortion of sound and video output.

 

I've attached the diagnostic log and i'll paste a couple snippets of the log files I believe may be helpful:

 

2017-01-17 19:34:30.086+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Windows 10' -S -machine pc-i440fx-2.5,accel=kvm,usb=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -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/4b6733a6-c5f8-50b1-416e-2844a5019f17_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 16384 -realtime mlock=on -smp 16,sockets=1,cores=8,threads=2 -uuid 4b6733a6-c5f8-50b1-416e-2844a5019f17 -nographic -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device nec-usb-xhci,id=usb,bus=pci.0,addr=0x7 -device ahci,id=sata0,bus=pci.0,addr=0x3 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/dev/disk/by-id/ata-Samsung_SSD_850_EVO_250GB_S21PNXAG664859P,format=raw,if=none,id=drive-sata0-0-2,cache=writeback -device ide-hd,bus=sata0.2,drive=drive-sata0-0-2,id=sata0-0-2,bootindex=1 -drive file=/mnt/user/isos/SW_DVD5_Win_Pro_10_1607_64BIT_English_MLF_X21-06988.ISO,format=raw,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,bootindex=2 -drive file=/mnt/user/isos/virtio-win-0.1.126.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:17:3a:15,bus=pci.0,addr=0x2 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev 'socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-Windows 10/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 vfio-pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device vfio-pci,host=02:00.0,id=hostdev1,bus=pci.0,addr=0x6 -device vfio-pci,host=81:00.0,id=hostdev2,bus=pci.0,addr=0x8 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 -msg timestamp=on
Domain id=23 is tainted: high-privileges
Domain id=23 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2017-01-17T19:35:01.037192Z qemu-system-x86_64: terminating on signal 15 from pid 5730
2017-01-17 19:35:02.797+0000: shutting down

 

Jan 17 19:34:29 Tower kernel: vgaarb: device changed decodes: PCI:0000:04:00.0,olddecodes=io+mem,decodes=io+mem:owns=none
Jan 17 19:34:30 Tower kernel: device vnet0 entered promiscuous mode
Jan 17 19:34:30 Tower kernel: br0: port 2(vnet0) entered forwarding state
Jan 17 19:34:30 Tower kernel: br0: port 2(vnet0) entered forwarding state
Jan 17 19:34:44 Tower kernel: vfio_ecap_init: 0000:04:00.0 hiding ecap 0x1e@0x258
Jan 17 19:34:44 Tower kernel: vfio-pci 0000:02:00.0: enabling device (0400 -> 0402)
Jan 17 19:34:45 Tower kernel: vfio-pci 0000:81:00.0: enabling device (0400 -> 0402)
Jan 17 19:34:55 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound
Jan 17 19:34:55 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound
Jan 17 19:35:01 Tower kernel: sdf: sdf1 sdf2 sdf3 sdf4
Jan 17 19:35:01 Tower kernel: br0: port 2(vnet0) entered disabled state
Jan 17 19:35:01 Tower kernel: device vnet0 left promiscuous mode
Jan 17 19:35:01 Tower kernel: br0: port 2(vnet0) entered disabled state
Jan 17 19:35:06 Tower kernel: vgaarb: device changed decodes: PCI:0000:04:00.0,olddecodes=io+mem,decodes=io+mem:owns=none

 

Any help would be really appreciated - I'm hitting a brick wall with this one.

 

Cheers!

tower-diagnostics-20170117-1937.zip

Anyone have any ideas with this one?

 

It's definitely this line I need to figure out:

 

2017-01-17T19:35:01.037192Z qemu-system-x86_64: terminating on signal 15 from pid 5730

 

How do I find out what pid 5730 is?

I don't think its the same, but I found my vm would hang randomly on startup but work second time too.  However mine showed as paused on the VM page.

 

I worked out that it was the i440 machine type causing my hangs.  When I selected 2.5 I got the hangs... when i downgraded to 2.3 the hangs went away.  No idea what the difference between the two is though.

same issue here, always 1st boot stops, 2nd boot just runs fine through ....

 

same behavior on 2 win10 VM´s here, 1 intel passthrough, 1 Nvidia passthrough.

 

Example Nvidia

 

2017-01-20 05:19:55.026+0000: starting up libvirt version: 2.4.0, qemu version: 2.7.0, hostname: AlsServer

LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=AlsMedia,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-10-AlsMedia/master-key.aes -machine pc-i440fx-2.7,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -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/eba4c457-6ff8-72c0-1fc3-55bb6a5c67a9_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 8192 -realtime mlock=off -smp 2,sockets=1,cores=2,threads=1 -uuid eba4c457-6ff8-72c0-1fc3-55bb6a5c67a9 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-10-AlsMedia/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device nec-usb-xhci,id=usb,=3,hostaddr=10,id=hostdev4,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on

Domain id=10 is tainted: high-privileges

Domain id=10 is tainted: host-cpu

char device redirected to /dev/pts/1 (label charserial0)

2017-01-20T05:20:19.897469Z qemu-system-x86_64: terminating on signal 15 from pid 4559

2017-01-20 05:20:22.121+0000: shutting down, reason=shutdown

 

hey guys,

 

you can try following:

 

- go to your BIOS

- set the PCIe Gen to Version 2

- boot Unraid

- boot your VM

 

This was a solution for me. Now every VM with passthrough is working fine.

 

Thanks for the advise.

 

Tried both suggestions:

 

1. Changed machine type from i440 v2.5 down to 2.4/2.3/2.2 - no change

2. BIOS already set to gen2 pci-e but changed to gen3 in case that helped - no change

 

Also checked BIOS firmware was up to date.

 

Issue still persists...

I think my vms booting now, installed quemu-gax64.msi, may try that.

Tried installing that msi but didn't make a difference. managed to find the PID that is apparently responsible though (noticed it lists them in Tools -> processes..

 

root      6043    1  0 11:27 ?        00:00:00 /usr/sbin/libvirtd -d -l -f /etc/libvirt/libvirtd.conf -p /var/run/libvirt/libvirtd.pid

 

Not sure if that helps narrow down the issue though!

Finally managed to at least solve this issue!

 

Instructions below for anyone else having the issue that might stumble on this thread:

 

Type Control Panel in the search box.

Click Control Panel.

Click Power Options.

Click Choose what the power buttons do.

Click Change settings that are currently unavailable.

Scroll down to Shutdown settings and uncheck Turn on fast startup.

Click Save changes.

I did cmd powercfg -h Off

Guess thats also a solution.

On 1/22/2017 at 7:42 AM, effingheck said:

Finally managed to at least solve this issue!

 

Instructions below for anyone else having the issue that might stumble on this thread:

 

Type Control Panel in the search box.

Click Control Panel.

Click Power Options.

Click Choose what the power buttons do.

Click Change settings that are currently unavailable.

Scroll down to Shutdown settings and uncheck Turn on fast startup.

Click Save changes.

I will try this tonight as im getting the same problem i will post my results. What i discovered was im only getting this error when i shut the VM down from within Windows. If i shut it down from the VM Manager in UNRAID then it starts up ok the next time. Problem only exists when i shut down the VM from within windows.

 

I also was re-watching the windows 10 vm install videos and i noticed i missed the installing the qemu-guest agent x64 driver. I wonder if that will help? I will try that tonight and report back.

 

EDIT: Changing the Windows FAST STARTUP to OFF fixed my re-boot problems. Thanks everyone!

Edited February 5, 20197 yr by alfredo_2020

I have the same issue but it happens with Windows, Linux and OSX VM's.

 

What would the the equivalent of "Windows FAST STARTUP to OFF" on Linux and OSX?