January 21, 201610 yr 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!
January 21, 201610 yr Could you share your XML and also a syslog (from settings)? It may be easier to just run the diagnostics (settings), and attach it (it will have even more info). Are you passing through a GPU to this VM? Define "crashing", BSOD, lockup?
January 23, 201610 yr Author Could you share your XML and also a syslog (from settings)? It may be easier to just run the diagnostics (settings), and attach it (it will have even more info). Are you passing through a GPU to this VM? Define "crashing", BSOD, lockup? 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
January 23, 201610 yr This might be stating the obvious, but have you checked the power management settings within Windows? It may be that it's hibernating and that is causing the machine to shutdown....
January 23, 201610 yr Author This might be stating the obvious, but have you checked the power management settings within Windows? It may be that it's hibernating and that is causing the machine to shutdown.... Thank you for the thought, yup I have checked that!
January 23, 201610 yr This might be stating the obvious, but have you checked the power management settings within Windows? It may be that it's hibernating and that is causing the machine to shutdown.... Thank you for the thought, yup I have checked that! Odd... So when you restart the VM does it say something in regards to recovering from a system crash or something along those lines? Normally Windows logs things like that and complains if it went down badly. Have you disabled the fast startup option that is in the power settings page?
January 23, 201610 yr Author 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>
January 24, 201610 yr Author How about the logs column under the VMs tab? 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.
January 24, 201610 yr How about the logs column under the VMs tab? 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. What does it say? You can also check the libvirt log under the VM Manager page (turn on help there).
January 30, 201610 yr Author 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?
Archived
This topic is now archived and is closed to further replies.