GoudaK Posted June 18, 2018 Share Posted June 18, 2018 (edited) Hi all, I’m having a problem with what has been a stable Win10 VM. After the 6.5.3 unRAID update my VM will refuse to boot, it just stays on the circle loading screen and will not progress. There also seems to be a windows update happening which might also be causing the problem? If I start up repair the VM it will boot once and then refuse to boot again (installs 1803 downloaded update), everything works except chrome when I get in once. My mate is having exactly the same drama as me also. Has anyone got a clue on what’s happening here? [EDIT] After a lot of mucking around it appears to be my USB headset... As soon as I pass my Astro A50 headset the VM will not boot or if I hot plug the VM becomes unresponsive. I have tried this with 2 separate VM's with the exact same result. The 4 cores attached to the VM go to 100% usage, as soon as I unplug the headset the VM is responsive and will boot. I have tried with a passed through USB3 card, hotplug via Libvert Hotplug and assigning to the VM both in the USB3 card and motherboard directly. This has been working fine for about 12 months and now refuses, any ideas? Here are the logs: 2018-06-19 09:21:35.003+0000: shutting down, reason=failed2018-06-19 09:22:06.164+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: TowerLC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-Windows 10/master-key.aes' -machine pc-i440fx-2.11,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/994d5b83-a351-3957-4b44-22794ad79b0b_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 16384 -realtime mlock=off -smp 8,sockets=1,cores=8,threads=1 -uuid 994d5b83-a351-3957-4b44-22794ad79b0b -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-2-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device icvice virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1b:f7:e0,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-2-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=09:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device vfio-pci,host=09:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=7,hostaddr=2,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=7,hostaddr=3,id=hostdev3,bus=usb.0,port=2 -device usb-host,hostbus=7,hostaddr=4,id=hostdev4,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on2018-06-19 09:22:06.164+0000: Domain id=2 is tainted: high-privileges2018-06-19 09:22:06.164+0000: Domain id=2 is tainted: host-cpu2018-06-19T09:22:06.197831Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)libusb: error [udev_hotplug_event] ignoring udev action bindlibusb: error [op_set_configuration] failed, error -1 errno 1102018-06-19T09:26:22.547059Z qemu-system-x86_64: libusb_set_configuration: -99 [OTHER]libusb: error [_open_sysfs_attr] open /sys/bus/usb/devices/5-1/bConfigurationValue failed ret=-1 errno=22018-06-19T09:27:47.873161Z qemu-system-x86_64: terminating on signal 15 from pid 11917 (/usr/sbin/libvirtd)2018-06-19 09:27:49.273+0000: shutting down, reason=destroyed2018-06-19 09:28:40.670+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: TowerLC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-Windows 10/master-key.aes' -machine pc-i440fx-2.11,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/994d5b83-a351-3957-4b44-22794ad79b0b_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 16384 -realtime mlock=off -smp 8,sockets=1,cores=8,threads=1 -uuid 994d5b83-a351-3957-4b44-22794ad79b0b -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device icvice virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1b:f7:e0,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-3-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=09:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device vfio-pci,host=09:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=7,hostaddr=2,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=7,hostaddr=3,id=hostdev3,bus=usb.0,port=2 -device usb-host,hostbus=7,hostaddr=4,id=hostdev4,bus=usb.0,port=3 -device usb-host,hostbus=5,hostaddr=12,id=hostdev5,bus=usb.0,port=4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on2018-06-19 09:28:40.670+0000: Domain id=3 is tainted: high-privileges2018-06-19 09:28:40.670+0000: Domain id=3 is tainted: host-cpu2018-06-19T09:28:40.707861Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)libusb: error [op_set_configuration] failed, error -1 errno 1102018-06-19T09:28:56.147061Z qemu-system-x86_64: libusb_set_configuration: -99 [OTHER]2018-06-19 09:30:06.755+0000: shutting down, reason=destroyed2018-06-19 09:33:16.097+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: TowerLC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4-Windows 10/master-key.aes' -machine pc-i440fx-2.11,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/994d5b83-a351-3957-4b44-22794ad79b0b_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 16384 -realtime mlock=off -smp 8,sockets=1,cores=8,threads=1 -uuid 994d5b83-a351-3957-4b44-22794ad79b0b -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-4-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device icvice virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1b:f7:e0,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-4-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=09:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device vfio-pci,host=09:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=7,hostaddr=2,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=7,hostaddr=3,id=hostdev3,bus=usb.0,port=2 -device usb-host,hostbus=7,hostaddr=4,id=hostdev4,bus=usb.0,port=3 -device usb-host,hostbus=7,hostaddr=5,id=hostdev5,bus=usb.0,port=4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on2018-06-19 09:33:16.097+0000: Domain id=4 is tainted: high-privileges2018-06-19 09:33:16.097+0000: Domain id=4 is tainted: host-cpu2018-06-19T09:33:16.133397Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)libusb: error [op_set_configuration] failed, error -1 errno 1102018-06-19T09:33:31.091058Z qemu-system-x86_64: libusb_set_configuration: -99 [OTHER]libusb: error [_open_sysfs_attr] open /sys/bus/usb/devices/7-2/bConfigurationValue failed ret=-1 errno=2libusb: error [udev_hotplug_event] ignoring udev action bindlibusb: error [op_set_configuration] failed, error -1 errno 1102018-06-19T09:39:21.299030Z qemu-system-x86_64: libusb_set_configuration: -99 [OTHER] Edited June 19, 2018 by GoudaK Quote Link to comment
GoudaK Posted June 18, 2018 Author Share Posted June 18, 2018 I’ve blocked the 1803 update and have successfully rebooted several times without issue... I can only pause the update for 35 days, is anyone else having these problems? Quote Link to comment
GoudaK Posted June 18, 2018 Author Share Posted June 18, 2018 (edited) So I spun up another Windows VM using VNC, I updated to latest windows build and it was working fine, rebooted several times without issue. This morning I tried to pass the GPU through and the VM will not boot with the same issue as above. All CPU cores assigned to the VM are maxed at 100%, however no booting will occur. I tried the original VM without GPU pass through and it boots fine. I've now updated this to the latest Windows build, it will boot without GPU passed through however will not boot with it passed. Could this perhaps been caused by the unRAID update? Edited June 18, 2018 by GoudaK Quote Link to comment
SSD Posted June 18, 2018 Share Posted June 18, 2018 I have successfully updated my Windows VM to 1803. Afterwards I had demonic sound, which was only fixed by updating the GPU drivers (Nvidia 1050 Ti) and rerunning the MSI utility. Now the audio seems perfect. Previously I had noticed an occasional drifting of audio sync with YouTube, which I have not seen since the update. But I also haven't done a lot of testing so that may still happen. I would advise, if possible, to reload the GPU drivers and see if it helps. Quote Link to comment
GoudaK Posted June 18, 2018 Author Share Posted June 18, 2018 Thanks, I'll give it a go... although with the new VM there were no Nvidia drivers installed at all and it refused to boot with GPU passthrough. Quote Link to comment
GoudaK Posted June 19, 2018 Author Share Posted June 19, 2018 After a lot of mucking around it appears to be my USB headset... As soon as I pass my Astro A50 headset the VM will not boot or if I hot plug the VM becomes unresponsive. I have tried this with 2 separate VM's with the exact same result. The 4 cores attached to the VM go to 100% usage, as soon as I unplug the headset the VM is responsive and will boot. Any ideas? Quote Link to comment
GoudaK Posted June 19, 2018 Author Share Posted June 19, 2018 I solved it by using a USB3 PCIE card... I cannot explain why that works... Quote Link to comment
Recommended Posts
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.