September 19, 20169 yr Hi, I have just upgraded to unRAID 6.2 and my VM has stopped working. It hangs as it boots. Sometimes it starts recovery mode but as soon as get to the screen which gives me the option to boot into safe mode, it locks up there and stops accepting keyboard/mouse inputs. I am at a loss for what to do, please could you provide assistance. Initially I was getting errors where the VM wouldn't start at all but I managed to get passed that by tweaking the syslinux.cfg with: label KVM/unRAID OS menu default kernel /bzimage append intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 pcie_acs_override=downstream initrd=/bzroot Specifically adding the "KVM/" on the first line and "intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 pcie_acs_override=downstream" on the last line. I tried setting up a second fresh windows VM without GPU (using VNC for graphics) and that also locks up when trying to boot into windows (the windows installer runs fine) Any assistance greatly appreciated. nova-diagnostics-20160918-1358.zip
September 19, 20169 yr Does it lock up completely or does it just stop accepting keyboard/mouse input? The syslinux line you added is for ACS override, did unraid work before without it? And when you disable ACS override (remove the lines you added from the syslinux config and restart) is HVM and IOMMU enabled?
September 19, 20169 yr Author It definitely locks up entirely so I have to force stop the VM, can tell because it has happened on the spinning Windows loading screen and the animation has frozen. Without those edits to the syslinux I get the following error when starting the VM: internal error: process exited while connecting to monitor: 2016-09-19T22:10:09.304450Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,id=hostdev0,x-vga=on,bus=pci.0,addr=0x5: vfio: failed to set iommu for container: Operation not permitted 2016-09-19T22:10:09.304476Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,id=hostdev0,x-vga=on,bus=pci.0,addr=0x5: vfio: failed to setup container for group 12 2016-09-19T22:10:09.304482Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,id=hostdev0,x-vga=on,bus=pci.0,addr=0x5: vfio: failed to get group 12 2016-09-19T22:10:09.304490Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,id=hostdev0,x-vga=on,bus=pci.0,addr=0x5: Device initialization failed Though unRAID still deems IOMMU & HVM as being enabled. I believe it was identified previously when I first tried using VM's with unRAID that there is a problem with the BIOS of my motherboard. For some reason I was able to get it working on the previous build of unRAID and my VM was stable. If it helps, this is the post I made when I first got unRAID and was encountering problems: https://lime-technology.com/forum/index.php?topic=45959.0 Please let me know if any further information is required to assist in identifying the cause of this problem. Thanks again
September 19, 20169 yr It looks like (i am not 100% sure) that vfio can't use your GPU and ACS override (IOMMU works so you shouldn't need ACS override) fixed it but also caused the problem in this version. In what slot is your GPU, are there any other GPUs in your server (in which slots are they) and did you try stubbing the GPU? Also please post the entire "PCI Devices" and "IOMMU Groups" from Tools -> System Devices.
September 20, 20169 yr Author The GPU I am trying to pass through is in the middle slot (second PCIE 16x slot down) In the top slot, a Nvidia GT 610 is there as the CPU/motherboard I am using does not have integrated graphics, so that is the display which allows me to see what unsaid is doing directly. As Requested, "PCI Devices" 00:00.0 Host bridge [0600]: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port [8086:3405] (rev 13) 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 13) 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 13) 00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 [8086:340e] (rev 13) 00:14.0 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers [8086:342e] (rev 13) 00:14.1 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers [8086:3422] (rev 13) 00:14.2 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers [8086:3423] (rev 13) 00:14.3 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub Throttle Registers [8086:3438] (rev 13) 00:1a.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a37] 00:1a.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a38] 00:1a.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a39] 00:1a.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 [8086:3a3c] 00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller [8086:3a3e] 00:1c.0 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 [8086:3a40] 00:1c.2 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 3 [8086:3a44] 00:1c.3 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 4 [8086:3a46] 00:1c.4 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5 [8086:3a48] 00:1d.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 [8086:3a34] 00:1d.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 [8086:3a35] 00:1d.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 [8086:3a36] 00:1d.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 [8086:3a3a] 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 90) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller [8086:3a16] 00:1f.2 SATA controller [0106]: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller [8086:3a22] 00:1f.3 SMBus [0c05]: Intel Corporation 82801JI (ICH10 Family) SMBus Controller [8086:3a30] 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) 02:00.1 Audio device [0403]: NVIDIA Corporation GF119 HDMI Audio Controller [10de:0e08] (rev a1) 03:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) 03:00.1 Audio device [0403]: NVIDIA Corporation GK106 HDMI Audio Controller [10de:0e0b] (rev a1) 04:00.0 SATA controller [0106]: JMicron Technology Corp. JMB363 SATA/IDE Controller [197b:2363] (rev 03) 04:00.1 IDE interface [0101]: JMicron Technology Corp. JMB363 SATA/IDE Controller [197b:2363] (rev 03) 05:00.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6315 Series Firewire Controller [1106:3403] 06:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 02) ff:00.0 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 QuickPath Architecture Generic Non-Core Registers [8086:2c41] (rev 05) ff:00.1 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 QuickPath Architecture System Address Decoder [8086:2c01] (rev 05) ff:02.0 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 QPI Link 0 [8086:2c10] (rev 05) ff:02.1 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 QPI Physical 0 [8086:2c11] (rev 05) ff:03.0 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller [8086:2c18] (rev 05) ff:03.1 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Target Address Decoder [8086:2c19] (rev 05) ff:03.4 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Test Registers [8086:2c1c] (rev 05) ff:04.0 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Control Registers [8086:2c20] (rev 05) ff:04.1 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Address Registers [8086:2c21] (rev 05) ff:04.2 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Rank Registers [8086:2c22] (rev 05) ff:04.3 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Thermal Control Registers [8086:2c23] (rev 05) ff:05.0 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Control Registers [8086:2c28] (rev 05) ff:05.1 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Address Registers [8086:2c29] (rev 05) ff:05.2 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Rank Registers [8086:2c2a] (rev 05) ff:05.3 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Thermal Control Registers [8086:2c2b] (rev 05) ff:06.0 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Control Registers [8086:2c30] (rev 05) ff:06.1 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Address Registers [8086:2c31] (rev 05) ff:06.2 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Rank Registers [8086:2c32] (rev 05) ff:06.3 Host bridge [0600]: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Thermal Control Registers [8086:2c33] (rev 05) -------- And IOMMU Groups: /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/2/devices/0000:00:03.0 /sys/kernel/iommu_groups/3/devices/0000:00:07.0 /sys/kernel/iommu_groups/4/devices/0000:00:14.0 /sys/kernel/iommu_groups/4/devices/0000:00:14.1 /sys/kernel/iommu_groups/4/devices/0000:00:14.2 /sys/kernel/iommu_groups/4/devices/0000:00:14.3 /sys/kernel/iommu_groups/5/devices/0000:00:1a.0 /sys/kernel/iommu_groups/5/devices/0000:00:1a.1 /sys/kernel/iommu_groups/5/devices/0000:00:1a.2 /sys/kernel/iommu_groups/5/devices/0000:00:1a.7 /sys/kernel/iommu_groups/6/devices/0000:00:1b.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.2 /sys/kernel/iommu_groups/7/devices/0000:00:1c.3 /sys/kernel/iommu_groups/7/devices/0000:00:1c.4 /sys/kernel/iommu_groups/7/devices/0000:04:00.0 /sys/kernel/iommu_groups/7/devices/0000:04:00.1 /sys/kernel/iommu_groups/7/devices/0000:05:00.0 /sys/kernel/iommu_groups/7/devices/0000:06:00.0 /sys/kernel/iommu_groups/8/devices/0000:00:1d.0 /sys/kernel/iommu_groups/8/devices/0000:00:1d.1 /sys/kernel/iommu_groups/8/devices/0000:00:1d.2 /sys/kernel/iommu_groups/8/devices/0000:00:1d.7 /sys/kernel/iommu_groups/9/devices/0000:00:1e.0 /sys/kernel/iommu_groups/10/devices/0000:00:1f.0 /sys/kernel/iommu_groups/10/devices/0000:00:1f.2 /sys/kernel/iommu_groups/10/devices/0000:00:1f.3 /sys/kernel/iommu_groups/11/devices/0000:02:00.0 /sys/kernel/iommu_groups/11/devices/0000:02:00.1 /sys/kernel/iommu_groups/12/devices/0000:03:00.0 /sys/kernel/iommu_groups/12/devices/0000:03:00.1 /sys/kernel/iommu_groups/13/devices/0000:ff:00.0 /sys/kernel/iommu_groups/13/devices/0000:ff:00.1 /sys/kernel/iommu_groups/14/devices/0000:ff:02.0 /sys/kernel/iommu_groups/14/devices/0000:ff:02.1 /sys/kernel/iommu_groups/15/devices/0000:ff:03.0 /sys/kernel/iommu_groups/15/devices/0000:ff:03.1 /sys/kernel/iommu_groups/15/devices/0000:ff:03.4 /sys/kernel/iommu_groups/16/devices/0000:ff:04.0 /sys/kernel/iommu_groups/16/devices/0000:ff:04.1 /sys/kernel/iommu_groups/16/devices/0000:ff:04.2 /sys/kernel/iommu_groups/16/devices/0000:ff:04.3 /sys/kernel/iommu_groups/17/devices/0000:ff:05.0 /sys/kernel/iommu_groups/17/devices/0000:ff:05.1 /sys/kernel/iommu_groups/17/devices/0000:ff:05.2 /sys/kernel/iommu_groups/17/devices/0000:ff:05.3 /sys/kernel/iommu_groups/18/devices/0000:ff:06.0 /sys/kernel/iommu_groups/18/devices/0000:ff:06.1 /sys/kernel/iommu_groups/18/devices/0000:ff:06.2 /sys/kernel/iommu_groups/18/devices/0000:ff:06.3 Thanks again for your help!
September 20, 20169 yr Reset the syslinux config to default, start the new VM that you created without GPU and wait for it to crash, post the log (Press "Log" in the top right corner while in the VMs tab before starting the vm and then copy and paste or screenshot everything after the VM crashed) and post the VM configuration. And how much ram does your server have? I think it might be two different problems that cause the VMs to crash.
September 20, 20169 yr Author Hi, thanks again for your response. I am running 12GB of RAM and allocating 6 - 8 GB to the VM I was uncertain which log you meant so this is log from the very top right after the VM locked up: Sep 20 17:44:15 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:15 Nova kernel: usb 2-1.2: reset high-speed USB device number 7 using ehci-pci Sep 20 17:44:16 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:18 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:18 Nova kernel: usb 2-1.2: reset high-speed USB device number 7 using ehci-pci Sep 20 17:44:18 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:19 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:20 Nova kernel: usb 2-1.2: reset high-speed USB device number 7 using ehci-pci Sep 20 17:44:20 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:21 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:21 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:24 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:24 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:25 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:25 Nova kernel: usb 2-1.2: reset high-speed USB device number 7 using ehci-pci Sep 20 17:44:25 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:26 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:26 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:27 Nova kernel: usb 2-1.2: reset high-speed USB device number 7 using ehci-pci Sep 20 17:44:27 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:27 Nova kernel: usb 2-1.2: reset high-speed USB device number 7 using ehci-pci Sep 20 17:44:27 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:29 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:29 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:30 Nova kernel: usb 2-1.2: reset high-speed USB device number 7 using ehci-pci Sep 20 17:44:30 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:30 Nova kernel: usb 2-1.2: reset high-speed USB device number 7 using ehci-pci Sep 20 17:44:30 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:31 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:31 Nova kernel: usb 2-1.2: reset high-speed USB device number 7 using ehci-pci Sep 20 17:44:31 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:32 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:33 Nova kernel: usb 2-1.2: reset high-speed USB device number 7 using ehci-pci Sep 20 17:44:33 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:33 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:34 Nova kernel: usb 2-1.1: reset low-speed USB device number 5 using ehci-pci Sep 20 17:44:35 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci Sep 20 17:44:35 Nova kernel: usb 2-1.3: reset full-speed USB device number 8 using ehci-pci ------ And the following is the log that was for/alongside the VM: 2016-09-20 16:34:19.634+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Nova 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/0ee92e75-5396-3dbe-dc80-a67049752864_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 6144 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 0ee92e75-5396-3dbe-dc80-a67049752864 -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 ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,masterbus=usb.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 -vnc 0.0.0.0:0,websocket=5700 -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0,addr=0x2 -device usb-host,hostbus=2,hostaddr=5,id=hostdev0 -device usb-host,hostbus=2,hostaddr=7,id=hostdev1 -device usb-host,hostbus=2,hostaddr=8,id=hostdev2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on Domain id=1 is tainted: high-privileges Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-09-20T16:35:16.941173Z qemu-system-x86_64: terminating on signal 15 from pid 3419 2016-09-20 16:35:17.341+0000: shutting down 2016-09-20 16:35:51.386+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Nova 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/0ee92e75-5396-3dbe-dc80-a67049752864_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 6144 -realtime mlock=off -smp 4,sockets=1,cores=2,threads=2 -uuid 0ee92e75-5396-3dbe-dc80-a67049752864 -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 ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,masterbus=usb.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 -vnc 0.0.0.0:0,websocket=5700 -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0,addr=0x2 -device usb-host,hostbus=2,hostaddr=5,id=hostdev0 -device usb-host,hostbus=2,hostaddr=7,id=hostdev1 -device usb-host,hostbus=2,hostaddr=8,id=hostdev2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on Domain id=2 is tainted: high-privileges Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH --------- And lastly copied from the VM config: <domain type='kvm'> <name>Windows 10</name> <uuid>0ee92e75-5396-3dbe-dc80-a67049752864</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>6291456</memory> <currentMemory unit='KiB'>6291456</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/0ee92e75-5396-3dbe-dc80-a67049752864_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor id='none'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/VM ISO/Windows10.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/VM ISO/virtio-win-0.1.118-2.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:45:b1:ed'/> <source bridge='virbr0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='connect'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc228'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc229'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> Thanks again for your help!
September 20, 20169 yr Looks like the problem might be caused by a problem with the a USB controller, do you have any usb devices passed through to the new VM?
September 20, 20169 yr Author Oh I do, Keyboard is USB, ot has a built in 2 port usb hub in which the Logitech unifying receiver for my mouse is connected (which is also passed through) Outside of that, nothing else is passed through
September 20, 20169 yr Author Thank you, that appears to be working !! I have no idea how you figured that out but I am extremely grateful! Problem is, does this mean I can't pass through any USB devices to my VM any more?
September 20, 20169 yr Thank you, that appears to be working !! I have no idea how you figured that out but I am extremely grateful! Problem is, does this mean I can't pass through any USB devices to my VM any more? Are you passing through the controller or just the USB devices?
September 20, 20169 yr Just the devices individually Open the config of the VM, enable advanced settings and change the USB mode to 3.0 (XHCI). The problem definitely has something to do with the usb device passthrough...
June 14, 20188 yr Ok so I am having the same exact problem please help and what do I need to do for you to help.
June 14, 20188 yr 5 minutes ago, bheast said: Ok so I am having the same exact problem please help and what do I need to do for you to help. You should start your own thread, with your diagnostics etc as very very rarely are VM lockups / resets the same from person to person, and are all highly dependent upon your configuration, your hardware, IOMMU groups, etc etc etc. Not to mention that this thread is almost 2 years old and is almost certainly not the version of unRaid that you are running.
June 14, 20188 yr 13 hours ago, bheast said: anyone? 14 hours ago, bheast said: I posted a new topic but no response Multiple reasons possible: - People looked at the diagnostics, and didn't have an answer - People who would possibly be able to help are either Sleeping At work Eating Dinner Playing with their dog and/or kids
Archived
This topic is now archived and is closed to further replies.