comfox

Hey Limetech can you please weigh in on this?

Anyone else have any ideas here? Can anyone tell me why the host needing memory is crashing my VM's?

Thanks for the suggestion on number one. Is there any way I can limit the amount of memory that unRAID can consume? This box has 16GB total and I am giving 13GB to the VM. This means I am giving 3GB to unRAID. My secondary unRAID only has 1GB of RAM and runs without issue (no VM on second unRAID, just straight up unRAID and docker running). Seems odd that there is such a hard delineation of memory management with KVM. All the other VM providers I have used have much better memory management and will not shut down a VM when the host needs more RAM

I have been using KVM to run a Windows 10 Machine for about 6 months now and while it works I find that the VM crashes 2 - 3 times a week. By crashing I mean the VM is just off, I can't RDP and the VM has the red box. In the VM 'Log' that is accessible through webGui this is all that shows: Domain id=1 is tainted: high-privileges Domain id=1 is tainted: custom-argv Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-04-08 18:15:39.513+0000: shutting down I am assuming that there are much more detailed logs for KVM that would point me in the direction as to why my VM's keep crashing but I don't know where to look for them. My guess is that it has something to do with memory, but that is just a hunch that I have no supporting information to prove. Are there any experts out there that wouldn't mind helping me? Here is my current VM XML in case that is helpful: <domain type='kvm' id='1' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Win 10 Main PC</name> <uuid>e43d49b3-00c0-a740-1250-341a6f1f11a4</uuid> <description>This is the main gaming rig in the office</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>13107200</memory> <currentMemory unit='KiB'>13107200</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>7</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='4'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='6'/> <vcpupin vcpu='6' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='7' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/VM_HDD_Lib/Win 10 Main PC/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:d9:23:a0'/> <source bridge='xenbr0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Win 10 Main PC.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x1532'/> <product id='0x011a'/> <address bus='3' device='4'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc24a'/> <address bus='3' device='3'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> Here is the current hardware listing in case that is helpful: 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d5) 00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 (rev d5) 00:1c.7 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1) 02:00.0 USB controller: Fresco Logic Device 1100 (rev 10) 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13) 05:00.0 PCI bridge: Pericom Semiconductor PI7C9X111SL PCIe-to-PCI Reversible Bridge (rev 02) 06:04.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 01) 07:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 08:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) I am passing through the Video Card (01:00.0 & 01:00.1) and the PCIx USB (02:00.0). I ahve PCIe ACS Override setting enabled. I have turned on the MSI patch. All drivers and Win10 are fully updated with latest patches and drivers.

So I found an old thread (https://lime-technology.com/forum/index.php?topic=42211.0) that said this could be caused my no not enough memory which shouldn't be a problem for me since I have 16GB of RAM installed. I checked on the 'Dashboard' page and saw my 'Memory usage' at 20% committed. That seemed high considering I was doing nothing. So I was thinking the KVM manager didn't release the memory properly so I found a website (http://www.upubuntu.com/2013/01/how-to-free-up-unused-memory-in.html) that suggested running these commands to free up memory sudo sysctl -w vm.drop_caches=3 and sudo sync && echo 3 | sudo tee /proc/sys/vm/drop_caches While I have no clue what they do, they successfully lowered my 'Memory usage' on the Dashboard to 13%. I clicked on the VM to start it and poof, it worked. Guess you mark this as resolved and maybe sticky this or add this knowledge to an FAQ on how to fix that specific error. Cheers!

Wouldn't the BTSync docker add on do this? Runs real-time and has the GUI

Hello All, I have been running my Windows 10 VM for 2 days and 1 hour and it hard crashed in the background while I was connected to it via RDP. I didn't see the crash, just went back to the RDP window and the connection was closed. I am now trying to start the VM back up but I am getting this an error. internal error: process exited while connecting to monitor: 2016-03-21T17:56:23.546456Z qemu-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory Anyone know what that means? VM Log 2016-03-19 15:30:12.644+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=1 is tainted: high-privileges Domain id=1 is tainted: custom-argv Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-03-21 17:34:44.261+0000: shutting down 2016-03-21 17:56:02.640+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=2 is tainted: high-privileges Domain id=2 is tainted: custom-argv Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-03-21T17:56:02.680486Z qemu-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory 2016-03-21 17:56:02.845+0000: shutting down 2016-03-21 17:56:23.507+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=3 is tainted: high-privileges Domain id=3 is tainted: custom-argv Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-03-21T17:56:23.546456Z qemu-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory 2016-03-21 17:56:23.711+0000: shutting down

Never mind, I just found the sticky topic about this. Trying it now!

Hey All, I am experiencing an issue that is causing my Win 10 KVM to become unusable. When my Plex Docker is encoding videos to sync to other devices the processing must be going through the roof because my Win10 KVM grinds to a halt. Is there a way to force Docker to use less processor power or restrict to only Core 0?

So the crashing had stopped all of a sudden, however today it is now back. Here is the log from the KVM...I don't find it helpful at all. 2016-01-22 01:14:57.748+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=1 is tainted: high-privileges Domain id=1 is tainted: custom-argv Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-01-22 18:15:39.513+0000: shutting down 2016-01-23 00:26:41.044+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=2 is tainted: high-privileges Domain id=2 is tainted: custom-argv Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-01-23 17:21:46.129+0000: shutting down 2016-01-23 21:45:03.122+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=3 is tainted: high-privileges Domain id=3 is tainted: custom-argv Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-01-30 07:35:13.075+0000: shutting down 2016-01-30 12:55:24.007+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=4 is tainted: high-privileges Domain id=4 is tainted: custom-argv Domain id=4 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-01-30 12:56:24.098+0000: shutting down 2016-01-30 12:58:17.046+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=5 is tainted: high-privileges Domain id=5 is tainted: custom-argv Domain id=5 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-01-30 12:59:49.780+0000: shutting down There is definitely some sort of "bug" going on because it appears that all is good for a while then "something" happens and all goes to hell. I then reboot all of unRAID and all is good again for a while. How can I go about troubleshooting this?

I recommend the MSI fix. I found it improved stability considerably once I put it in.

Are you passing through both the GPU AND the HDMI Audio? I found without both my Win 10 VM would crash. I also had to enable the MSI on both the GPU and the Audio for Windows to finally play nice. While I am still encountering random crashing, my config is stable enough to use daily.

The one that you access from the GUI? I click on that and window that pops up has very little information in it, like maybe 15 lines.

Is there not a log in unRAID to show why KVM crashes?

Yea windows logs it as a crash, nothing else really of value though. Crash 1 Log Name: System Source: EventLog Date: 1/23/2016 4:45:23 PM Event ID: 6008 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DESKTOP-OA5P99N Description: The previous system shutdown at 12:07:04 PM on ?1/?23/?2016 was unexpected. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="EventLog" /> <EventID Qualifiers="32768">6008</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-01-23T21:45:23.574192400Z" /> <EventRecordID>2829</EventRecordID> <Channel>System</Channel> <Computer>DESKTOP-OA5P99N</Computer> <Security /> </System> <EventData> <Data>12:07:04 PM</Data> <Data>?1/?23/?2016</Data> <Data> </Data> <Data> </Data> <Data>60008</Data> <Data> </Data> <Data> </Data> <Binary>E0070100060017000C00070004007A00E0070100060017001100070004007A00600900003C000000010000006009000001000000B00400000100000000000000</Binary> </EventData> </Event> Crash 2 Log Name: System Source: EventLog Date: 1/22/2016 7:27:04 PM Event ID: 6008 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DESKTOP-OA5P99N Description: The previous system shutdown at 12:55:20 PM on ?1/?22/?2016 was unexpected. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="EventLog" /> <EventID Qualifiers="32768">6008</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-01-23T00:27:04.108267300Z" /> <EventRecordID>2727</EventRecordID> <Channel>System</Channel> <Computer>DESKTOP-OA5P99N</Computer> <Security /> </System> <EventData> <Data>12:55:20 PM</Data> <Data>?1/?22/?2016</Data> <Data> </Data> <Data> </Data> <Data>60009</Data> <Data> </Data> <Data> </Data> <Binary>E0070100050016000C00370014009103E0070100050016001100370014009103600900003C000000010000006009000001000000B00400000100000000000000</Binary> </EventData> </Event> Crash 3 Log Name: System Source: EventLog Date: 1/21/2016 8:15:20 PM Event ID: 6008 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DESKTOP-OA5P99N Description: The previous system shutdown at 12:07:21 AM on ?1/?21/?2016 was unexpected. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="EventLog" /> <EventID Qualifiers="32768">6008</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-01-22T01:15:20.885653800Z" /> <EventRecordID>2649</EventRecordID> <Channel>System</Channel> <Computer>DESKTOP-OA5P99N</Computer> <Security /> </System> <EventData> <Data>12:07:21 AM</Data> <Data>?1/?21/?2016</Data> <Data> </Data> <Data> </Data> <Data>88810</Data> <Data> </Data> <Data> </Data> <Binary>E0070100040015000000070015004401E0070100040015000500070015004401600900003C000000010000006009000001000000B00400000100000000000000</Binary> </EventData> </Event> Crash 4 Log Name: System Source: EventLog Date: 1/19/2016 11:27:21 PM Event ID: 6008 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DESKTOP-OA5P99N Description: The previous system shutdown at 11:13:00 PM on ?1/?19/?2016 was unexpected. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="EventLog" /> <EventID Qualifiers="32768">6008</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-01-20T04:27:21.216576000Z" /> <EventRecordID>2556</EventRecordID> <Channel>System</Channel> <Computer>DESKTOP-OA5P99N</Computer> <Security /> </System> <EventData> <Data>11:13:00 PM</Data> <Data>?1/?19/?2016</Data> <Data> </Data> <Data> </Data> <Data>9</Data> <Data> </Data> <Data> </Data> <Binary>E00701000200130017000D0000003403E00701000300140004000D00000034033C0000003C000000000000000000000000000000000000000100000000000000</Binary> </EventData> </Event> Crash 5 Log Name: System Source: EventLog Date: 1/19/2016 11:13:00 PM Event ID: 6008 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DESKTOP-OA5P99N Description: The previous system shutdown at 3:19:58 AM on ?1/?17/?2016 was unexpected. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="EventLog" /> <EventID Qualifiers="32768">6008</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-01-20T04:13:00.820216900Z" /> <EventRecordID>2506</EventRecordID> <Channel>System</Channel> <Computer>DESKTOP-OA5P99N</Computer> <Security /> </System> <EventData> <Data>3:19:58 AM</Data> <Data>?1/?17/?2016</Data> <Data> </Data> <Data> </Data> <Data>177610</Data> <Data> </Data> <Data> </Data> <Binary>E007010000001100030013003A00EB00E007010000001100080013003A00EB00600900003C000000010000006009000001000000B00400000100000000000000</Binary> </EventData> </Event>

Thank you for the thought, yup I have checked that!

Hey bungee91, thanks for the response. Here is all the information you asked for. VM XML <domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Win 10 Main PC</name> <uuid>e43d49b3-00c0-a740-1250-341a6f1f11a4</uuid> <description>This is the main gaming rig in the office</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>13107200</memory> <currentMemory unit='KiB'>13107200</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>7</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='6'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='7' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/VM_HDD_Lib/Win 10 Main PC/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:d9:23:a0'/> <source bridge='xenbr0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Win 10 Main PC.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x1532'/> <product id='0x011a'/> <address bus='1' device='4'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc24a'/> <address bus='1' device='3'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> I am passing through the following USB PCIe card GPU PCIe ACS Override: Yes crashing means, I wake up in the morning and the VM is in an off state. No BSOD, Not input at all, the monitor is black and when I got to the VM page the red box is in the VM showing it is off. syslog is attached as a zip. Thanks in advance for any help. syslog.zip

Hey Everyone, I am experiencing an unknown issue that is resulting in my Win 10 VM crashing. Can anyone point me in the right direction to start troubleshooting it? Is there a location where logs are keps for the VM specifically? I don't know much about KVM but I assume when it crashes a log entry is made somewhere right? Thanks in advance!

Found the solution from another thread where JobP posted to a solution https://lime-technology.com/forum/index.php?topic=43782.0

In my quest to conquer KVM I am once again in need of the communities help. After some number of hours of running my Windows 10 VM all of my audio and video will play in slow motion. Doesn't matter what application is making the sound or playing a video it is all in slow motion. I haven't been able to pinpoint exactly how many hours after boot up this starts, but I generally find it the next day. I do not use sleep, I simply have the monitor shut off. Any ideas or thoughts? Here is my VM XML <domain type='kvm' id='1' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Win 10 Main PC</name> <uuid>e43d49b3-00c0-a740-1250-341a6f1f11a4</uuid> <description>This is the main gaming rig in the office</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>13107200</memory> <currentMemory unit='KiB'>13107200</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>7</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='6'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='7' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/VM_HDD_Lib/Win 10 Main PC/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:d9:23:a0'/> <source bridge='xenbr0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Win 10 Main PC.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x152d'/> <product id='0x0551'/> <address bus='2' device='3'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x0984'/> <product id='0x0040'/> <address bus='1' device='6'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc24a'/> <address bus='1' device='4'/> </source> <alias name='hostdev2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x1532'/> <product id='0x011a'/> <address bus='1' device='3'/> </source> <alias name='hostdev3'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> I am passing through both the audio and video of my nVidia GTX 970 as well as two USB 3.0 HDD's, a Razor keybord and a Logitech mouse. I thought it might be a drive issue but I am using the most up to date drivers from nVidia. I can fix this with a reboot of the VM but I would prefer not having to reboot my VM daily. Thanks in advance!

Thanks Johnnie.black. Looks like this card is going back. Appreciate the link!

Hey ashman70 thanks for the thoughts. As I stated though the drive is recognized in the BIOS of the device so the jumpers are definately set right. Also the card is detecting the drive as a physical device just fine. Took a picture of the cards BIOS showing the drive.

I have installed my Vantec UGT-ST644R PCIe card in my machine to expand the drive capacity however unRAID appears to not want to find the drive that is attached to the card. The motherboard has detected the card and the drive just fine. I see the drive listed in the bootup during the Cards BIOS screen. unRAID has detected the card just fine as you can see by my PCI device list below. 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.2 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x4 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 (rev d5) 00:1c.7 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1) 02:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11) 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13) 05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) As you can see unRAID has detected the card as PCI device 02:00.0. Any ideas from anyone? As an aside the drive works fine. I have plugged it into another SATA controller and the drive is detected just fine. Also I have used the drive in a Windows box and it works just fine. Also tried the drive in a USB 3.0 enclosure and the drive works just fine. Also added a syslog in the attachments. syslog.zip

Excellent! Is everything still running now that it's been a couple of days? So far so good!

I have an ASUS GeForce GTX 970 Turbo which I am passing through to a Window 10 VM. I have had a tough go with getting the VM to be stable however I think I appear to have a working, stable VM now. Goober07 pointed out to me that you have to pass through BOTH the GPU and the Audio portion for this to be stable. If you don't pass through both you will have some serious stability issues.