Shutting down VM causes unRaid to CRASH


FalconX

33 posts in this topic Last Reply

Recommended Posts

Posting here as I didn't get much luck in General support.

 

Hey Everyone,

 

So recently I've started having issues with my Windows 10 VM. Every time I send a shutdown signal from the VM list to shutdown the VM (or even if I go and shutdown from the windowsitself) it completely crashes unRaid. The webgui becomes unresponsive and I cannot ssh into my tower. I have to force shutdown the server by holding down the power button.

 

This started happening shortly after I setup the GPU pass-through (nvidia GT 710) to the windows VM. Before this, I could shut it down no problem. Not sure if this is related or not.

 

Things I have tried:

 

  • Assign more RAM to the VM (8GB currently) (non gaming VM, just running Blue Iris and a screen capture)
  • Increase vdisk size
  • Increase core count (5 cores assigned, 10 threads)
  • Change initial memory to match max memory (8GB)
  • Turned off Hyper - V
  • Used a GT 710 Graphics ROM BIOS (The GPU was working fine without this)
  • Changed:
    • Disk Cache 'vm.dirty_background_ratio' (%): 1
    • Disk Cache 'vm.dirty_ratio' (%): 2
  • The VM task manager shows 2GB used out of 8GB assigned to it, this can't be a memory issue can it?

 

For the life of me I cannot figure this out. I can't capture any syslog because everything crashes before anything is able to be written.

The only thing that will occasionally show up in the syslog when shutting the VM down is the following:

php-fpm[14569]: [WARNING] [pool www] server reached max_children setting (20), consider raising it

The VM will boot normally and if I shut it down within a few minutes, it shuts down no problem. This only happens when I try to shut it down the following day or when it has been up and running for awhile.

 

System:

Supermicro - X8DTL

Dual L5640's

40GB RAM

 

Windows 10 VM xml

 

Any help would be greatly appreciated. Thank you!

 

  Quote

<domain type='kvm'>
  <name>Windows 10</name>
  <uuid>92210a11-aef7-64bf-0f40-d3509f8dd9e4</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>10</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='7'/>
    <vcpupin vcpu='1' cpuset='19'/>
    <vcpupin vcpu='2' cpuset='8'/>
    <vcpupin vcpu='3' cpuset='20'/>
    <vcpupin vcpu='4' cpuset='9'/>
    <vcpupin vcpu='5' cpuset='21'/>
    <vcpupin vcpu='6' cpuset='10'/>
    <vcpupin vcpu='7' cpuset='22'/>
    <vcpupin vcpu='8' cpuset='11'/>
    <vcpupin vcpu='9' cpuset='23'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/92210a11-aef7-64bf-0f40-d3509f8dd9e4_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='5' threads='2'/>
  </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/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/disks/evo/domains/blueiris/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Win10_1703_English_x64.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/isos/virtio-win-0.1.141-1.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='0x03' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:17:30:36'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/isos/vbios/MSI.GT710.2048.160112.rom'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </memballoon>
  </devices>
</domain>
 

 

 

Update:

 

I spun a new Win10 VM install with the Nvdia GT 710 pass through (4 cores, 4GB ram). The GPU shows up fine on device manager once windows installed the drivers for it. No issues there.

Left it running overnight again. Logged into the VM this morning, shutdown the VM and unraid webGUI slowly starts to hang, then completely becomes unresponsive. No SSH no GUI.

I had the syslog window open, the only message that came up again:

 

php-fpm[14569]: [WARNING] [pool www] server reached max_children setting (20), consider raising it

 

Tried to log in through IPMI and execute a graceful shutdown but it just froze after this message:

gracefully shutting down php-fpm.................................................failed

force quitting

and then it just hung there for 15 minutes before I forcefully shut it off.

I don't know if I'm leaking memory somewhere, I'm almost certain it has something to do with the GPU passthrough.

 

I also tried using Fix Common Problems troubleshooting mode but when it crashes, it doesn't even up dumping a syslog or a tail log at all.

 

Not sure where to go from here...

 

 

Edited by FalconX
Link to post

Post full diagnostics zip. Also list what else is running on the server.

 

Consider trying the “allow unsafe interrupts” syslinux change as a shot in the dark (fixed a problem I had with a vm shitting down tanking a system because the bios freaked out about the gpu changing states.)

Link to post
2 hours ago, 1812 said:

Post full diagnostics zip. Also list what else is running on the server.

 

Consider trying the “allow unsafe interrupts” syslinux change as a shot in the dark (fixed a problem I had with a vm shitting down tanking a system because the bios freaked out about the gpu changing states.)

 

I've added 

append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot

to my syslinux.cfg

Unfortunately my diagnostics do not say anything since unraid crashes and won't dump a diagnostics file. The last thing that shows up on the log is this:

php-fpm[14569]: [WARNING] [pool www] server reached max_children setting (20), consider raising it

 

Plex,Sonarr,Radarr,LetsEncrypt,Organizr,Nextcloud,Pihole,rtorrentvpn,tautulli,unifi,unms,ddclient,jackett,mariadb,netdata are all running on the server.

System usually sits at 10% cpu load and memory at 24%

 

1 hour ago, AnnabellaRenee87 said:

May want to make sure the MSI interrupts are turned on too.

Sent from my SM-G955U using Tapatalk
 

I've enabled MSI interrupts (it was off)

Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+

 

I will let it run overnight again and try shutting down tomorrow. Thanks for the suggestions!
 

Link to post
  • 3 months later...

I didn't save the exact error, but basically after enabling it and restarting the server I could not start the VM. I went in and tried to edit the VM and it wouldn't let me make any changes ( had to make another VM with same vdisks, probably was corrupted some how). Since my last post I had another crash. I went ahead and forced a reboot, set MSI interrupts again and reboot. Started the array up and saw that some of the IOMMU groups changed. Edited the VM and it saved successfully, started up and now I'm just testing. Seems good SO FAR.

Link to post

So I decided to shut down my VM today to do some maintenance and back up some things, seems the MSI interrupts did NOT work as it just crashed my server once again. I'm going to need some serious guidance on how to have this setup correctly because every VM shut down causing a crash is not going to work for me. 

Link to post

Hi @slimshizn   sorry to hear that you are having problems with your server.

Reading through your post I was a little confused reading about the MSI interrupts. I am guessing that you are adding to your syslinux config file/setting in vm settings and allowing unsafe interrupts. Unsafe interrupts are used when your server doesn't support interrupt remapping, this is different to MSI interrupts in the VM. I know too many bloody interrupts gets confusing :)

The MSI interrupts are enabled in the os and are normally used when the sound isn't working correctly and it breaks up a bit. Its commonly known as demonic sound. But this wouldn't help you using this in your vms when it comes to the vm and the crashing.

 

So to troubleshoot, lets start from the beginning. Can you try the following, please? Remove all of the custom settings in settings/VM Manager (and or syslinux config if you manually added things)

so both PCIe ACS override and VFIO allow unsafe interrupts set them both to disabled and reboot your server.

Once rebooted please go to tools/system devices and copy your PCI Devices and IOMMU Groups into this thread so we can see them.

That way we can see what gpu you have and its natural iommu grouping.

Then with your gpu passed through to the VM (and its sound counterpart) start the VM. If you get an error copy that error and also paste it into this thread.

Then we can advise you on what settings to try next. :)

 

 

 

 

Link to post

Thank you for the reply @SpaceInvaderOne , and before I started just wanted to let you know that your videos have helped tremendously till this point. So, as you requested I disabled VFIO allow unsafe interrupts and PCIe ACS override and rebooted the server. Here are the IOMMU Groups. For ease of view and to save time for you I went ahead and highlighted the GPU and the USB hub I'm working with.
 

Quote

 

IOMMU group 0:[8086:0e00] 00:00.0 Host bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 DMI2 (rev 04)

IOMMU group 1:[8086:0e02] 00:01.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 1a (rev 04)

IOMMU group 2:[8086:0e03] 00:01.1 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 1b (rev 04)

IOMMU group 3:[8086:0e04] 00:02.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 2a (rev 04)

IOMMU group 4:[8086:0e06] 00:02.2 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 2c (rev 04)

IOMMU group 5:[8086:0e08] 00:03.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3a (rev 04)

IOMMU group 6:[8086:0e20] 00:04.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 0 (rev 04)

[8086:0e21] 00:04.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 1 (rev 04)

[8086:0e22] 00:04.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 2 (rev 04)

[8086:0e23] 00:04.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 3 (rev 04)

[8086:0e24] 00:04.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 4 (rev 04)

[8086:0e25] 00:04.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 5 (rev 04)

[8086:0e26] 00:04.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 6 (rev 04)

[8086:0e27] 00:04.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 7 (rev 04)

IOMMU group 7:[8086:0e28] 00:05.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 VTd/Memory Map/Misc (rev 04)

[8086:0e2a] 00:05.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IIO RAS (rev 04)

[8086:0e2c] 00:05.4 PIC: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IOAPIC (rev 04)

IOMMU group 8:[8086:1d3e] 00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Virtual Root Port (rev 06)

IOMMU group 9:[8086:1d3a] 00:16.0 Communication controller: Intel Corporation C600/X79 series chipset MEI Controller #1 (rev 05)

[8086:1d3b] 00:16.1 Communication controller: Intel Corporation C600/X79 series chipset MEI Controller #2 (rev 05)

IOMMU group 10:[8086:1d2d] 00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 (rev 06)

IOMMU group 11:[8086:1d10] 00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 1 (rev b6)

IOMMU group 12:[8086:1d1a] 00:1c.5 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 6 (rev b6)

IOMMU group 13:[8086:1d1e] 00:1c.7 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 8 (rev b6)

IOMMU group 14:[8086:1d26] 00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 (rev 06)

IOMMU group 15:[8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)

IOMMU group 16:[8086:1d41] 00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller (rev 06)

[8086:1d02] 00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset 6-Port SATA AHCI Controller (rev 06)

[8086:1d22] 00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host Controller (rev 06)

[8086:1d24] 00:1f.6 Signal processing controller: Intel Corporation C600/X79 series chipset Thermal Management Controller (rev 06)

IOMMU group 17:[1000:0072] 02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

IOMMU group 18:[126f:2262] 03:00.0 Non-Volatile memory controller: Silicon Motion, Inc. Device 2262 (rev 03)

IOMMU group 19:[10de:1b80] 05:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)

[10de:10f0] 05:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)

IOMMU group 20:[8086:1528] 07:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01)

IOMMU group 21:[8086:1528] 07:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01)

IOMMU group 22:[1b73:1100] 09:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10)

IOMMU group 23:[1a03:1150] 0a:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 02)

[1a03:2000] 0b:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 21)

IOMMU group 24:[8086:0e80] 7f:08.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Link 0 (rev 04)

IOMMU group 25:[8086:0e90] 7f:09.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Link 1 (rev 04)

IOMMU group 26:[8086:0ec0] 7f:0a.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 0 (rev 04)

[8086:0ec1] 7f:0a.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 1 (rev 04)

[8086:0ec2] 7f:0a.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 2 (rev 04)

[8086:0ec3] 7f:0a.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 3 (rev 04)

IOMMU group 27:[8086:0e1e] 7f:0b.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers (rev 04)

[8086:0e1f] 7f:0b.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers (rev 04)

IOMMU group 28:[8086:0ee0] 7f:0c.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee2] 7f:0c.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee4] 7f:0c.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee6] 7f:0c.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee8] 7f:0c.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

IOMMU group 29:[8086:0ee1] 7f:0d.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee3] 7f:0d.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee5] 7f:0d.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee7] 7f:0d.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee9] 7f:0d.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

IOMMU group 30:[8086:0ea0] 7f:0e.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 0 (rev 04)

[8086:0e30] 7f:0e.1 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 0 (rev 04)

IOMMU group 31:[8086:0ea8] 7f:0f.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Target Address/Thermal Registers (rev 04)

[8086:0e71] 7f:0f.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 RAS Registers (rev 04)

[8086:0eaa] 7f:0f.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)

[8086:0eab] 7f:0f.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)

[8086:0eac] 7f:0f.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)

[8086:0ead] 7f:0f.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)

IOMMU group 32:[8086:0eb0] 7f:10.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 0 (rev 04)

[8086:0eb1] 7f:10.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 1 (rev 04)

[8086:0eb2] 7f:10.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 0 (rev 04)

[8086:0eb3] 7f:10.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 1 (rev 04)

[8086:0eb4] 7f:10.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 2 (rev 04)

[8086:0eb5] 7f:10.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 3 (rev 04)

[8086:0eb6] 7f:10.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 2 (rev 04)

[8086:0eb7] 7f:10.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 3 (rev 04)

IOMMU group 33:[8086:0e1d] 7f:13.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 R2PCIe (rev 04)

[8086:0e34] 7f:13.1 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 R2PCIe (rev 04)

[8086:0e81] 7f:13.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Ring Registers (rev 04)

[8086:0e36] 7f:13.5 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Ring Performance Ring Monitoring (rev 04)

IOMMU group 34:[8086:0ec8] 7f:16.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 System Address Decoder (rev 04)

[8086:0ec9] 7f:16.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers (rev 04)

[8086:0eca] 7f:16.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers (rev 04)

IOMMU group 35:[8086:0e01] 80:00.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port in DMI2 Mode (rev 04)

IOMMU group 36:[8086:0e02] 80:01.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 1a (rev 04)

IOMMU group 37:[8086:0e03] 80:01.1 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 1b (rev 04)

IOMMU group 38:[8086:0e04] 80:02.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 2a (rev 04)

IOMMU group 39:[8086:0e06] 80:02.2 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 2c (rev 04)

IOMMU group 40:[8086:0e08] 80:03.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3a (rev 04)

IOMMU group 41:[8086:0e0a] 80:03.2 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3c (rev 04)

IOMMU group 42:[8086:0e20] 80:04.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 0 (rev 04)

[8086:0e21] 80:04.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 1 (rev 04)

[8086:0e22] 80:04.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 2 (rev 04)

[8086:0e23] 80:04.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 3 (rev 04)

[8086:0e24] 80:04.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 4 (rev 04)

[8086:0e25] 80:04.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 5 (rev 04)

[8086:0e26] 80:04.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 6 (rev 04)

[8086:0e27] 80:04.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 7 (rev 04)

IOMMU group 43:[8086:0e28] 80:05.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 VTd/Memory Map/Misc (rev 04)

[8086:0e2a] 80:05.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IIO RAS (rev 04)

[8086:0e2c] 80:05.4 PIC: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IOAPIC (rev 04)

IOMMU group 44:[8086:0e80] ff:08.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Link 0 (rev 04)

IOMMU group 45:[8086:0e90] ff:09.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Link 1 (rev 04)

IOMMU group 46:[8086:0ec0] ff:0a.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 0 (rev 04)

[8086:0ec1] ff:0a.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 1 (rev 04)

[8086:0ec2] ff:0a.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 2 (rev 04)

[8086:0ec3] ff:0a.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 3 (rev 04)

IOMMU group 47:[8086:0e1e] ff:0b.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers (rev 04)

[8086:0e1f] ff:0b.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers (rev 04)

IOMMU group 48:[8086:0ee0] ff:0c.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee2] ff:0c.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee4] ff:0c.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee6] ff:0c.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee8] ff:0c.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

IOMMU group 49:[8086:0ee1] ff:0d.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee3] ff:0d.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee5] ff:0d.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee7] ff:0d.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

[8086:0ee9] ff:0d.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)

IOMMU group 50:[8086:0ea0] ff:0e.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 0 (rev 04)

[8086:0e30] ff:0e.1 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 0 (rev 04)

IOMMU group 51:[8086:0ea8] ff:0f.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Target Address/Thermal Registers (rev 04)

[8086:0e71] ff:0f.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 RAS Registers (rev 04)

[8086:0eaa] ff:0f.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)

[8086:0eab] ff:0f.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)

[8086:0eac] ff:0f.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)

[8086:0ead] ff:0f.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)

IOMMU group 52:[8086:0eb0] ff:10.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 0 (rev 04)

[8086:0eb1] ff:10.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 1 (rev 04)

[8086:0eb2] ff:10.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 0 (rev 04)

[8086:0eb3] ff:10.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 1 (rev 04)

[8086:0eb4] ff:10.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 2 (rev 04)

[8086:0eb5] ff:10.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 3 (rev 04)

[8086:0eb6] ff:10.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 2 (rev 04)

[8086:0eb7] ff:10.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 3 (rev 04)

IOMMU group 53:[8086:0e1d] ff:13.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 R2PCIe (rev 04)

[8086:0e34] ff:13.1 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 R2PCIe (rev 04)

[8086:0e81] ff:13.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Ring Registers (rev 04)

[8086:0e36] ff:13.5 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Ring Performance Ring Monitoring (rev 04)

IOMMU group 54:[8086:0ec8] ff:16.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 System Address Decoder (rev 04)

[8086:0ec9] ff:16.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers (rev 04)

[8086:0eca] ff:16.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers (rev 04)

 


Also as a test I tried something out prior to updating to 6.6.6 today. I logged out completely off windows on the VM, then shut it down. And to my surprise my server did NOT lock up. I would like to continue to figure out and test what the problem may be (as a admin stated this is probably hardware related) but for now that seems like the only work around I have at this time.

Edit: After starting the aforementioned VM after this point, there was no error. I have not ran into an error starting it since a few crashes ago when I had my USB get corrupted and the VM needed to be re created. Since then there has been no problem starting it.

Edit, spoke too soon. Crashed again after a shut down after logging out first.

 

Edited by slimshizn
Link to post

Hi, @slimshizn thanks for posting that.

looking at your iommu groups you do not need to use the PCIe acs override patch for your iommu. the grouping is fine how it is. Also if you don't get an error when starting the VM then you don't need to enable the unsafe interrupts either. So that's good news.

 

I think your problem of the crash is related to the USB controller: Fresco Logic FL1100 USB 3.0 Host Controller

If I remember @CHBMB discovered that this chipset doesn't play nicely with supermicro motherboards and would cause a crash.  Please try removing the USB card from the server and do some testing and see if that resolves your problem.

 

Edit --  found post where CHBMB discussed this findings 

 

Link to post

I'll take the controller out of the mix and see what happens. Also not sure if you had seen it but I have this all setup with a Gigabyte GA-7PESH2, not the supermicro board I have in my signature. Thanks for linking the topic I'll take a look and report back here after I do some testing.

Link to post

@SpaceInvaderOne Alright so here's what I've done, instead of passing through the entire PCI USB controller it allowed me to pass through single devices that I had on the controller.

First I rebooted the server, then before starting the VM I plugged in said single devices. I then went to the VM and selected the devices and saved and started.

 In 6.5.3 I wasn't able to do that, so since then there must have been updates allowing the devices to be passed through like that. I have since rebooted with no crashing of the server BUT I did get this error during the reboot.

Quote

libusb: error [udev_hotplug_event] ignoring udev action bind
libusb: error [udev_hotplug_event] ignoring udev action bind

Although this error happened and it took a bit longer to reboot it seems to be working without any other ill effects. 

image.png.e6e1f76f9277a60b87dedc61a12a5867.png
I'm thinking it might be that bluetooth dongle?

Edited by slimshizn
Link to post

Well although I was able to pass the external SSD through and it works, the USB Dongle and the Bluetooth Dongle both are not working in this configuration so that is a shame.

This may or may not help but here is a syslog snippet

 

Quote

Dec  7 11:31:40 Gaming kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1c.5/0000:09:00.0/usb3/3-3/3-3.4/3-3.4:1.0/0003:046D:C539.0009/input/input12
Dec  7 11:31:40 Gaming kernel: hid-generic 0003:046D:C539.0009: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:09:00.0-3.4/input0
Dec  7 11:31:40 Gaming kernel: input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:1c.5/0000:09:00.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:046D:C539.000A/input/input13
Dec  7 11:31:40 Gaming kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:1c.5/0000:09:00.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:046D:C539.000A/input/input14
Dec  7 11:31:40 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:31:40 Gaming kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:1c.5/0000:09:00.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:046D:C539.000A/input/input15
Dec  7 11:31:40 Gaming kernel: hid-generic 0003:046D:C539.000A: input,hiddev96,hidraw3: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:09:00.0-3.4/input1
Dec  7 11:31:40 Gaming kernel: hid-generic 0003:046D:C539.000B: hiddev98,hidraw4: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:09:00.0-3.4/input2
Dec  7 11:31:41 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:31:45 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:31:46 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:31:46 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:31:49 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:31:50 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:31:50 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:31:50 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:31:51 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:31:51 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:31:51 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:31:53 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:31:53 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:31:54 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:31:54 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:31:54 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:31:54 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:31:55 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:31:56 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:31:56 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:31:56 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:34:00 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:34:00 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:37:00 Gaming root: Fix Common Problems Version 2018.11.03
Dec  7 11:37:14 Gaming root: Fix Common Problems: Warning: Template URL for docker application HDDTemp is missing. ** Ignored
Dec  7 11:39:35 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:39:36 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:39:36 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:39:37 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:39:41 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:39:42 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:39:42 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:39:54 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:39:54 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:39:54 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:39:55 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:39:55 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:39:55 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:39:56 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:39:58 Gaming emhttpd: req (3): csrf_token=****************&title=Log+for%3AWindows+10&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=libvirt%2Fqemu%2FWindows+10.log
Dec  7 11:39:58 Gaming emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log libvirt/qemu/Windows 10.log
Dec  7 11:39:58 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:39:58 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:39:58 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:39:59 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:39:59 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:39:59 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:40:00 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:40:01 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:40:01 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:40:01 Gaming kernel: usb 3-4: reset full-speed USB device number 5 using xhci_hcd
Dec  7 11:40:19 Gaming emhttpd: req (4): csrf_token=****************&title=Log+for%3AWindows+10&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=libvirt%2Fqemu%2FWindows+10.log
Dec  7 11:40:19 Gaming emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log libvirt/qemu/Windows 10.log
Dec  7 11:42:01 Gaming kernel: usb 2-1-port5: disabled by hub (EMI?), re-enabling...
Dec  7 11:42:01 Gaming kernel: usb 2-1.5: USB disconnect, device number 6
Dec  7 11:42:01 Gaming kernel: usb 2-1.5: new low-speed USB device number 7 using ehci-pci
Dec  7 11:42:01 Gaming kernel: hid-generic 0003:09AE:2012.000C: hiddev99,hidraw5: USB HID v1.10 Device [Tripp Lite  Tripp Lite UPS ] on usb-0000:00:1d.0-1.5/input0
Dec  7 11:42:02 Gaming usbhid-ups[8699]: nut_libusb_get_interrupt: No such device (it may have been disconnected).
Dec  7 11:44:25 Gaming kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd
Dec  7 11:46:36 Gaming emhttpd: req (5): csrf_token=****************&title=Log+for%3AWindows+10&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=libvirt%2Fqemu%2FWindows+10.log
Dec  7 11:46:36 Gaming emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log libvirt/qemu/Windows 10.log
Dec  7 11:52:37 Gaming emhttpd: req (6): csrf_token=****************&title=Log+for%3AWindows+10&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=libvirt%2Fqemu%2FWindows+10.log
Dec  7 11:52:37 Gaming emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log libvirt/qemu/Windows 10.log
Dec  7 12:00:09 Gaming emhttpd: req (7): csrf_token=****************&title=Log+for%3AWindows+10&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=libvirt%2Fqemu%2FWindows+10.log
Dec  7 12:00:09 Gaming emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log libvirt/qemu/Windows 10.log
Dec  7 12:20:09 Gaming emhttpd: req (8): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog
Dec  7 12:20:09 Gaming emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

 

Edited by slimshizn
Link to post
Quote

Dec 18 10:44:23 Gaming kernel: RBP: ffffc90008403c68 R08: 0000000000600000 R09: ffff88046f421dc0
Dec 18 10:44:23 Gaming kernel: R10: 000000000000009c R11: 0000000000000026 R12: 0000000000000270
Dec 18 10:44:23 Gaming kernel: R13: ffff88046f421dc0 R14: 0000000000000026 R15: ffff88046f427400
Dec 18 10:44:23 Gaming kernel: FS: 000014fd9d8c4580(0000) GS:ffff88046f880000(0000) knlGS:0000000000000000
Dec 18 10:44:23 Gaming kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 18 10:44:23 Gaming kernel: CR2: 000014fd9c02e000 CR3: 00000003730d6006 CR4: 00000000001626e0
Dec 18 10:44:23 Gaming kernel: Call Trace:
Dec 18 10:44:23 Gaming kernel: _raw_spin_lock+0x16/0x19
Dec 18 10:44:23 Gaming kernel: qi_submit_sync+0x265/0x2db
Dec 18 10:44:23 Gaming kernel: modify_irte+0xe3/0x129
Dec 18 10:44:23 Gaming kernel: intel_irq_remapping_deactivate+0x2d/0x47
Dec 18 10:44:23 Gaming kernel: __irq_domain_deactivate_irq+0x27/0x33
Dec 18 10:44:23 Gaming kernel: irq_domain_deactivate_irq+0x15/0x22
Dec 18 10:44:23 Gaming kernel: __free_irq+0x10a/0x216
Dec 18 10:44:23 Gaming kernel: free_irq+0x42/0x59
Dec 18 10:44:23 Gaming kernel: vfio_intx_set_signal+0x2e/0x189
Dec 18 10:44:23 Gaming kernel: vfio_intx_disable+0x2f/0x4c
Dec 18 10:44:23 Gaming kernel: vfio_pci_set_intx_trigger+0x27/0x128
Dec 18 10:44:23 Gaming kernel: vfio_pci_ioctl+0x4e1/0x974
Dec 18 10:44:23 Gaming kernel: ? _copy_from_user+0x2f/0x4d
Dec 18 10:44:23 Gaming kernel: ? eventfd_write+0x89/0x1d3
Dec 18 10:44:23 Gaming kernel: ? __seccomp_filter+0x39/0x1ed
Dec 18 10:44:23 Gaming kernel: vfs_ioctl+0x19/0x26
Dec 18 10:44:23 Gaming kernel: do_vfs_ioctl+0x518/0x540
Dec 18 10:44:23 Gaming kernel: ksys_ioctl+0x39/0x58
Dec 18 10:44:23 Gaming kernel: __x64_sys_ioctl+0x11/0x14
Dec 18 10:44:23 Gaming kernel: do_syscall_64+0x57/0xe6
Dec 18 10:44:23 Gaming kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Dec 18 10:44:23 Gaming kernel: RIP: 0033:0x14fda0af5427
Dec 18 10:44:23 Gaming kernel: Code: 00 00 90 48 8b 05 69 0a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 39 0a 0d 00 f7 d8 64 89 01 48 
Dec 18 10:44:23 Gaming kernel: RSP: 002b:00007ffc4fd866d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Dec 18 10:44:23 Gaming kernel: RAX: ffffffffffffffda RBX: 000014fb1413ec00 RCX: 000014fda0af5427
Dec 18 10:44:23 Gaming kernel: RDX: 00007ffc4fd866e0 RSI: 0000000000003b6e RDI: 000000000000003e
Dec 18 10:44:23 Gaming kernel: RBP: 000014fb1413f5b0 R08: 0000000000000000 R09: 0000000000000000
Dec 18 10:44:23 Gaming kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 000014fb1413f7c0
Dec 18 10:44:23 Gaming kernel: R13: 0000555ba451f058 R14: 0000555ba451e32a R15: 0000000280000000

Had a call trace today after trying to reboot the VM. The WebGUI is not accessible and I can not SSH in.

Link to post

So I force rebooted and started the parity sync. I changed some things around. I kept the usb 3.0 external SSD on the usb hub, moved the bluetooth dongle and wireless mouse dongle to usb 2.0 ports and moved a few things around to make it work. Started it up and haven't seen an error or usb disconnect since. I'll see how this works for a while and in the meantime look for a different USB hub.

Link to post
  • 9 months later...

 

On 12/18/2018 at 6:17 PM, slimshizn said:

So I force rebooted and started the parity sync. I changed some things around. I kept the usb 3.0 external SSD on the usb hub, moved the bluetooth dongle and wireless mouse dongle to usb 2.0 ports and moved a few things around to make it work. Started it up and haven't seen an error or usb disconnect since. I'll see how this works for a while and in the meantime look for a different USB hub.

Did you ever find a solution for the problem?

Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.