Package Details: linux-vfio 4.16.3-1

Git Clone URL: (read-only)
Package Base: linux-vfio
Description: The Linux-vfio kernel and modules
Upstream URL:
Keywords: acs arbiter assignment gpu i915 kvm override passthrough pci qemu vfio vga
Licenses: GPL2
Submitter: zman0900
Maintainer: zman0900 (markzz)
Last Packager: markzz
Votes: 45
Popularity: 2.120069
First Submitted: 2015-01-30 06:41
Last Updated: 2018-04-20 18:59

Pinned Comments

markzz commented on 2017-12-14 06:10

(4.14.5+) Because Arch itself has dropped i686 support, I have removed i686 from the PKGBUILD and there is no config file either.

electricprism commented on 2016-01-04 04:30

Requires importing GPG Keys to build

# Linus Torvalds
gpg --recv-keys 79BE3E4300411886

# Greg Kroah-Hartman (Linux kernel stable release signing key)
gpg --recv-keys 38DBBDC86092693E

Latest Comments

markzz commented on 2018-04-13 15:59

When you build this PKGBUILD, you will get the three packages. As for how pacaur or ANY other aur helper works, I cannot say.

mcardillo55 commented on 2018-04-13 07:16

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?


markzz commented on 2018-04-06 16:30

Dehir: What?

Dehir commented on 2018-04-06 15:18

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

markzz commented on 2018-03-08 21:25

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.

c3924754 commented on 2018-03-08 21:19

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 .

markzz commented on 2018-02-10 01:51

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.

cinna commented on 2018-02-10 01:39

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

markzz commented on 2018-02-09 19:46

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

zatricky commented on 2018-02-08 20:19

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

All comments