Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - linux-vfio

Package Base Details: linux-vfio

Git Clone URL: https://aur-dev.archlinux.org/linux-vfio.git (read-only)
Keywords: acs arbiter assignment gpu i915 kvm override passthrough pci qemu vfio vga
Submitter: zman0900
Maintainer: zman0900 (markzz)
Last Packager: markzz
Votes: 28
Popularity: 2.995029
First Submitted: 2015-01-30 06:41
Last Updated: 2016-12-10 05:37

Pinned Comments

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

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

ohetfi commented on 2016-01-17 01:46

Hmm, that's weird. It seems that I'm the only one who has this issue. My guest is a Windows 10 guest, I put all my cores/threads on this guest (6 cores with 12 threads). The Tianocore splash screen took the same amount of time as with 4.1.15, but Windows loading took a while with all my threads on the Linux host are maxed. I put 24 GB of memory to it. Probably that's the case, what are you guest memory? Let's see if I can improve the boot performance if I reduce the memory size.

zman0900 commented on 2016-01-17 01:30

I haven't tried the latest mainline. I did notice with 4.4 that cpu usage maxes out 2 cores for a second or 2 during boot, but it seems to actually boot faster for me. The tianocore screen doesn't even time to show now when it used to appear for 3-5 seconds. Running windows 8.1 in the guest.

ohetfi commented on 2016-01-17 01:28

The patch for the bug has been merged since 4.4rc7 [1]. Although it can now boot successfully, I still felt the boot time is considerably slower and took higher CPU usage than in previous 4.1.15 kernel. Have you experienced the similar behavior in the latest mainline kernel?

[1] https://bugzilla.kernel.org/show_bug.cgi?id=107561

zman0900 commented on 2016-01-17 00:39

I usually keep this package in sync with the main Arch package, but I have recently built 4.4 and for the first time since 4.1 it is actually working to boot a VM with OVMF and pcie passthrough. I am running git version of OVMF (17560.ccdf8bc), qemu (2.5.0.r43284.5a57acb), and libvirt (1.3.1.rc2.3.g8f0a157 - custom package from my github), so it may or may not work with the repo versions.

Before upgrading, consider that this package is very closely based on the main Arch package which hasn't been released yet. You are taking the same risk as running the testing repo. It is possible that it could contain some system-destroying bug that you would normally not be exposed to because it would be fixed by the time it is released. You have been warned.

markzz commented on 2016-01-09 05:52

Pssst, the PKGBUILD states you are at pkgrel=2 but the .SRCINFO isn't reflecting that change. Might you re-run mksrcinfo?

markzz commented on 2016-01-04 04:41

@electricprism, that information is in the PKGBUILD.

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

zman0900 commented on 2015-11-22 06:31

You need to actually read the error messages above to see what the problem is. You are probably getting the same issue that gets comes up constantly for any aur package using signed sources - you don't have the public keys in your key ring. https://wiki.archlinux.org/index.php/Makepkg#Signature_checking

markzz commented on 2015-11-22 01:04

I do know for a fact that this package builds.

If you cannot build this (it may be because you're using something like yaourt and you have not enough ram), you can use my repository and install it from there. A direct link to the information for the repository [1] (so you can add to your pacman.conf if you wish) and a direct link to the package [2] and its signature (key ID 3CADDFDD) below [3] (for x86_64 only).

[1] https://wiki.archlinux.org/index.php/Unofficial_user_repositories#markzz
[2] http://repo.markzz.com/arch/markzz/x86_64/linux-vfio-4.2.5-1-x86_64.pkg.tar.xz
[3] http://repo.markzz.com/arch/markzz/x86_64/linux-vfio-4.2.5-1-x86_64.pkg.tar.xz.sig

lolwtfidk commented on 2015-11-22 01:00

Thats odd, installing from your repo worked fine, but I get ' A failure occurred in prepare()' when building it manually.