PCI device in use by driver QEMU

surfshack66 · September 26, 2016

Windows 10 VM can't start because a pci device is in use by driver QEMU (used in another VM). I'm confused why I'm receiving this error because im not using this particular pci device in this VM.

SpaceInvaderOne · September 26, 2016

please post your error message and your iommu groups and your pci devices from sysdevs

surfshack66 · September 26, 2016

please post your error message and your iommu groups and your pci devices from sysdevs

Error Message:

Execution error

Requested operation is not valid: PCI device 0000:04:00.0 is in use by driver QEMU, domain pfSense

IOMMU groups:

IOMMU Groups

/sys/kernel/iommu_groups/0/devices/0000:00:00.0
/sys/kernel/iommu_groups/1/devices/0000:00:01.0
/sys/kernel/iommu_groups/1/devices/0000:00:01.1
/sys/kernel/iommu_groups/1/devices/0000:01:00.0
/sys/kernel/iommu_groups/1/devices/0000:01:00.1
/sys/kernel/iommu_groups/1/devices/0000:02:00.0
/sys/kernel/iommu_groups/1/devices/0000:03:02.0
/sys/kernel/iommu_groups/1/devices/0000:03:04.0
/sys/kernel/iommu_groups/1/devices/0000:04:00.0
/sys/kernel/iommu_groups/1/devices/0000:04:00.1
/sys/kernel/iommu_groups/1/devices/0000:05:00.0
/sys/kernel/iommu_groups/1/devices/0000:05:00.1
/sys/kernel/iommu_groups/2/devices/0000:00:02.0
/sys/kernel/iommu_groups/3/devices/0000:00:03.0
/sys/kernel/iommu_groups/4/devices/0000:00:14.0
/sys/kernel/iommu_groups/5/devices/0000:00:16.0
/sys/kernel/iommu_groups/6/devices/0000:00:1a.0
/sys/kernel/iommu_groups/7/devices/0000:00:1b.0
/sys/kernel/iommu_groups/8/devices/0000:00:1c.0
/sys/kernel/iommu_groups/9/devices/0000:00:1c.3
/sys/kernel/iommu_groups/10/devices/0000:00:1c.5
/sys/kernel/iommu_groups/11/devices/0000:00:1d.0
/sys/kernel/iommu_groups/12/devices/0000:00:1f.0
/sys/kernel/iommu_groups/12/devices/0000:00:1f.2
/sys/kernel/iommu_groups/12/devices/0000:00:1f.3
/sys/kernel/iommu_groups/13/devices/0000:07:00.0
/sys/kernel/iommu_groups/14/devices/0000:08:00.0

PCI devices:

PCI Devices

00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
00:01.1 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller [8086:0c05] (rev 06)
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06)
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB xHCI Controller [8086:8cb1]
00:16.0 Communication controller [0780]: Intel Corporation 9 Series Chipset Family ME Interface #1 [8086:8cba]
00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 [8086:8cad]
00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset Family HD Audio Controller [8086:8ca0]
00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 [8086:8c90] (rev d0)
00:1c.3 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 [8086:8c96] (rev d0)
00:1c.5 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 6 [8086:8c9a] (rev d0)
00:1d.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 [8086:8ca6]
00:1f.0 ISA bridge [0601]: Intel Corporation 9 Series Chipset Family Z97 LPC Controller [8086:8cc4]
00:1f.2 SATA controller [0106]: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] [8086:8c82]
00:1f.3 SMBus [0c05]: Intel Corporation 9 Series Chipset Family SMBus Controller [8086:8ca2]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1)
01:00.1 Audio device [0403]: NVIDIA Corporation GM204 High Definition Audio Controller [10de:0fbb] (rev a1)
02:00.0 PCI bridge [0604]: Integrated Device Technology, Inc. [iDT] PES12N3A PCI Express Switch [111d:8018] (rev 0e)
03:02.0 PCI bridge [0604]: Integrated Device Technology, Inc. [iDT] PES12N3A PCI Express Switch [111d:8018] (rev 0e)
03:04.0 PCI bridge [0604]: Integrated Device Technology, Inc. [iDT] PES12N3A PCI Express Switch [111d:8018] (rev 0e)
04:00.0 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) [8086:10bc] (rev 06)
04:00.1 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) [8086:10bc] (rev 06)
05:00.0 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) [8086:10bc] (rev 06)
05:00.1 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) [8086:10bc] (rev 06)
07:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller [1969:e091] (rev 13)
08:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]

Windows 10 VM XML

<domain type='kvm'>
  <name>Windows 10</name>
  <uuid>5452f3a7-e756-9635-6ed6-4296c1817b09</uuid>
  <description>Workstation</description>
  <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/>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
    <vcpupin vcpu='1' cpuset='3'/>
    <vcpupin vcpu='2' cpuset='6'/>
    <vcpupin vcpu='3' cpuset='7'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor id='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='2' threads='2'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/vdisks/Windows 10/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/Windows 10 Enterprise VL X64 v1511 en-US March 2016/W10Ent.VLX64.en-US.Mar2016.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.118-2.iso'/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='nec-xhci'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </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:08:6c:41'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <source mode='connect'/>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
      </source>
      <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='0x01' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x1af3'/>
        <product id='0x0001'/>
      </source>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x2516'/>
        <product id='0x0004'/>
      </source>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </memballoon>
  </devices>
</domain>

"Offending" VM XML:

<domain type='kvm' id='2'>
  <name>pfSense</name>
  <uuid>bd84c85a-3e93-761c-ee2a-f9ae6e1d46c6</uuid>
  <description>pfSense Router / Firewall</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="linux.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>1</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-2.3'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='1' threads='1'/>
  </cpu>
  <clock offset='utc'>
    <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/user/vdisks/pfSense/vdisk1.img'/>
      <backingStore/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <alias name='virtio-disk2'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/ISOs/pfSense-LiveCD-2.2.6-RELEASE-amd64-20151221-1450.iso'/>
      <backingStore/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <alias name='sata0-0-0'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <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'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='sata' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'>
      <alias name='pcie.0'/>
    </controller>
    <controller type='pci' index='1' model='dmi-to-pci-bridge'>
      <model name='i82801b11-bridge'/>
      <alias name='pci.1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
    </controller>
    <controller type='pci' index='2' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='2'/>
      <alias name='pci.2'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:30:ed:0d'/>
      <source bridge='virbr0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x01' 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/domain-pfSense/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x04' slot='0x00' function='0x1'/>
      </source>
      <alias name='hostdev1'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev2'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x05' slot='0x00' function='0x1'/>
      </source>
      <alias name='hostdev3'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/>
    </hostdev>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x08' function='0x0'/>
    </memballoon>
  </devices>
</domain>

bungee91 · September 26, 2016

It's happening because you're requesting 1:00:0 and 1:00:1 which are listed in IOMMU group 1.

Everything within the same group must be passed to the VM, or stubbed (not used, bound to a placeholder).

The message seems a bit odd, however 4:00:0 is in group 1, along with the device your attempting to use in this VM.

You have a lot of items in group 1, you can try relocating it to another slot (may move the group), or use the ACS override setting.

Either way, you have to get that device isolated (in a different group) to assign it to the VM.

surfshack66 · September 26, 2016

It's happening because you're requesting 1:00:0 and 1:00:1 which are listed in IOMMU group 1.

Everything within the same group must be passed to the VM, or stubbed (not used, bound to a placeholder).

The message seems a bit odd, however 4:00:0 is in group 1, along with the device your attempting to use in this VM.

You have a lot of items in group 1, you can try relocating it to another slot (may move the group), or use the ACS override setting.

Either way, you have to get that device isolated (in a different group) to assign it to the VM.

Thanks. Looks like the groups changed since updating from 6.1.9 to 6.2 because everything worked fine before that. Also, I had a similar issue before and turned the ACS override setting on, so it's odd that the groups combined again.

surfshack66 · September 26, 2016

Is there any way to change the IOMMU groups without physically moving the devices?

BobPhoenix · September 26, 2016

It's happening because you're requesting 1:00:0 and 1:00:1 which are listed in IOMMU group 1.

Everything within the same group must be passed to the VM, or stubbed (not used, bound to a placeholder).

The message seems a bit odd, however 4:00:0 is in group 1, along with the device your attempting to use in this VM.

You have a lot of items in group 1, you can try relocating it to another slot (may move the group), or use the ACS override setting.

Either way, you have to get that device isolated (in a different group) to assign it to the VM.

Thanks. Looks like the groups changed since updating from 6.1.9 to 6.2 because everything worked fine before that. Also, I had a similar issue before and turned the ACS override setting on, so it's odd that the groups combined again.

When you upgraded to 6.2 your ACS override setting may have gotten turned off. I would try turning it off and back on if you find it showing as being ON.

surfshack66 · September 26, 2016

I've tried rebooting several times with the setting turned on and off but every time I go to the VM Manager settings. It says "You must reboot for changes to take effect".

If I change the setting to no and "apply" the message disappears. If I change it from no to yes then apply the message appears, so I'll reboot but the message persists.

Any ideas why this is happening?

BobPhoenix · September 26, 2016

I've tried rebooting several times with the setting turned on and off but every time I go to the VM Manager settings. It says "You must reboot for changes to take effect".

If I change the setting to no and "apply" the message disappears. If I change it from no to yes then apply the message appears, so I'll reboot but the message persists.

Any ideas why this is happening?

You got my only idea - Sorry.

JorgeB · September 26, 2016

You can check on the wegGUI, click on the flash drive, Syslinux configuration will look similar to this:

default /syslinux/menu.c32

menu title Lime Technology, Inc.

prompt 0

timeout 50

label unRAID OS

menu default

kernel /bzimage

append pci-stub.ids=8086:10d3 pcie_acs_override=downstream initrd=/bzroot

label unRAID OS GUI Mode

kernel /bzimage

append initrd=/bzroot,/bzroot-gui

label unRAID OS Safe Mode (no plugins, no GUI)

kernel /bzimage

append initrd=/bzroot unraidsafemode

label Memtest86+

kernel /memtest

If the highlighted text is present it's on.

surfshack66 · September 27, 2016

Thanks for the tip. Unfortunately, it is on. Even worse, I changed the slot of the NIC and it remained in the same IOUMMU group. I'm not sure what to do at this point and I'm still confused why it changed after the upgrade. I also tried turning VMs off and rebooting but no luck.

Any other way to force an IOMMU group change?

SpaceInvaderOne · September 27, 2016

Thanks for the tip. Unfortunately, it is on. Even worse, I changed the slot of the NIC and it remained in the same IOUMMU group. I'm not sure what to do at this point and I'm still confused why it changed after the upgrade. I also tried turning VMs off and rebooting but no luck.

Any other way to force an IOMMU group change?

Ok what version were you on before you upgraded. I would guess 6.19?

The fact your iommu groups have changed (this is my guess and i am sure others here will know more than me) is the different kernel. I think the upgrade from kernel 4.1 to 4.4 for you has effected your iommu groups.

KERNEL             UNRAID 
version 4.4.19     stable 6.2
———————————————-
version 4.4.19     rc5

version 4.4.18     rc4

version 4.4.15     rc2

version 4.4.14     rc1

version 4.4.13     beta 23

version 4.4.13     beta 22

version 4.4.6      beta 21

version 4.4.6      beta 20

version 4.4.5      beta 19

version 4.4.4      beta 18
————————————————
version 4.1.18     6.19

Above is the different kernels from recent unraids.

I notice that you have Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller

What cpu are you using?

Now I have heard the Xeon E3-1200 v3 series does not support ACS on the PCIe root ports although most other Xeons dot. So they need a kernel with the ACS Override patch. Also Skylake systems attempted to implement ACS on the PCH root ports, but it isnt quite right.

I think that the patched kernel isnt working for you on this newer kernel but my understanding of all this is very limited and hopefully someone here will read your thread with more knowledge.

You should maybe email Limetech and ask them about your problem or to look at this thread and reply here?

surfshack66 · September 27, 2016

Thanks @gridrunner

Yes, I was on 6.1.9 before and I'm using an Intel i7-4790K.

surfshack66 · September 28, 2016

The fact your iommu groups have changed (this is my guess and i am sure others here will know more than me) is the different kernel. I think the upgrade from kernel 4.1 to 4.4 for you has effected your iommu groups.
KERNEL             UNRAID 
version 4.4.19     stable 6.2
———————————————-
version 4.4.19     rc5

version 4.4.18     rc4

version 4.4.15     rc2

version 4.4.14     rc1

version 4.4.13     beta 23

version 4.4.13     beta 22

version 4.4.6      beta 21

version 4.4.6      beta 20

version 4.4.5      beta 19

version 4.4.4      beta 18
————————————————
version 4.1.18     6.19

So the latest stable linux kernel is 4.7.5 as of 9/24. Do we plan on upgrading to that at some point? Is there even a way to test that upgrading the kernel with affect the IOMMU groups again?

I have a workaround for now using the OS GUI and connecting to my windows vm via VNC, but its less than ideal.

Any other suggestions/input?

surfshack66 · September 30, 2016

If I boot into GUI mode, does this mean pcie_acs_override is disabled?

default /syslinux/menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append pcie_acs_override=downstream pci-stub.ids=8086:10bc initrd=/bzroot
label unRAID OS GUI Mode
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui
label unRAID OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest

Also, what is the default syslinux config? I edited this prior to the upgrade to stub the NIC but now it can be handled directly in the VM config

itimpi · September 30, 2016

If I boot into GUI mode, does this mean pcie_acs_override is disabled?
default /syslinux/menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append pcie_acs_override=downstream pci-stub.ids=8086:10bc initrd=/bzroot
label unRAID OS GUI Mode
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui
label unRAID OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest
Also, what is the default syslinux config? I edited this prior to the upgrade to stub the NIC but now it can be handled directly in the VM config

Yes. If you wanted it in GUI mode as well you would need to add it to the append line associate with GUI mode.

As far a I can see the addition of the acs_override to the non-GUI mode boot is the only change from the default syslinux.zip. You could always look in the ZIp download from the LimeTech site if you wanted to check the default contents of the file.

surfshack66 · September 30, 2016

Well that was the issue. I added that into the gui mode and the IOMMU groups reflected the change.

Thanks for the help. This issue is solved.

PCI device in use by driver QEMU

Recommended Posts

surfshack66

Link to comment

SpaceInvaderOne

Link to comment

surfshack66

Link to comment

bungee91

Link to comment

surfshack66

Link to comment

surfshack66

Link to comment

BobPhoenix

Link to comment

surfshack66

Link to comment

BobPhoenix

Link to comment

JorgeB

Link to comment

surfshack66

Link to comment

SpaceInvaderOne

Link to comment

surfshack66

Link to comment

surfshack66

Link to comment

surfshack66

Link to comment

itimpi

Link to comment

surfshack66

Link to comment

Join the conversation