Arch Linux User Repository

• Leaving eclairvoyant's comment pinned because it contains some useful information.
• Patch policy is different, but similar.
  • Primary purpose of this package are the ACS override and i915 VGA arbiter patches.
  • Upstream Arch patches will be applied to maintain parity with the standard kernel.
  • No other patches will be added.
• Package does have options that can be changed, like building with clang or disabling Arch patches.
  • Defaults will match Arch packages, except when incompatible with this package's primary patches.
  • Options are subject to change. Read PKGBUILD for details.
• Avoid commenting and flagging at the same time for the same issue.
  • Flag for common issues with standard solutions, like new releases, key changes, etc.
  • Comment for issues requiring explanation or debugging.
    • Use a pastebin for blocks of text more than a few lines.

This package exists for the specific purpose of adding ported patches based on those originally created by Alex Williamson for:

• Bypassing the default IOMMU grouping by overriding PCIe ACS support, and

• Enabling VGA arbitration support on Intel iGPUs.

Arbitrary patches will not be added.

Refer to the wiki on PCI passthrough and this blog post on IOMMU groups for risks/caveats before using this package.

Regular AUR etiquette applies as well (knowledge of makepkg and searching the wiki/Arch forums is expected, and AUR helpers or Arch-based distros that are not Arch Linux are unsupported).

Does the kernel need to be rebuilt to install linux-vfio-headers? For example, I run pacaur -S linux-vfio, it compiles and installs the kernel. Then I run pacaur -S linux-vfio-headers, it compiles the kernel again before installing the headers. Aren't the headers just extracted from the tarball?

Thanks

Dehir: What?

IF there is every possible to get realtime kernel with vfio same time :P

If either of you can get a core dump, I can investigate, but I don't know what else to tell you because I do not have the same hardware as you.

I can also confirm that with 4.11.4+ I cannot start my VMs that have a dedicated GPU. Experiencing output very similar to @cinna .

cinna: None of those functions in the call trace are in the patches that this kernel provide. I would either file a bug with Arch or with upstream.

I'm having a similar issue as zatricky where a VM refuses to launch when I have a dedicated gpu attached. Here's a relevant dmesg when I attempt to launch it. As for my hardware I'm running a Ryzen processor with a dedicated GPU for my host and another for my VMs

https://gist.github.com/anonymous/650925d4d58f7fd689b951f99c5d35f5

zatricky: Are you using an Intel iGPU for the host? Also, some relevant dmesg output would be helpful.

Latest package 4.15.1-1 resulted in sporadic errors from libvirtd when attempting to launch VM with dedicated GPU: Feb 08 22:08:04 <hostname> libvirtd[612]: 2018-02-08 20:08:04.406+0000: 612: error : virNetSocketReadWire:1808 : End of file while reading data: Input/output error</hostname>

Other VMs (not using GPU) were functional. From the moment I attempted to start the dedicated-GPU VM, virsh commands would no longer complete and virt-manager would become unresponsive.

Downgraded to 4.14.11-1 - all is working again.

• Z68MA-G45 (MS-7676)
• i7 3770
• AMD Radeon R9 380

Sorry about the lack of updates (if only I had unlimited time). I am currently building and testing 4.15 and you can expect it by this coming Friday.

EDIT: It is up and I need i915 users to tell me if everything's okay.