Package Details: linux-vfio 6.10.10-1

Git Clone URL: https://aur.archlinux.org/linux-vfio.git (read-only, click to copy)
Package Base: linux-vfio
Description: The Linux kernel and modules (ACS override and i915 VGA arbiter patches)
Upstream URL: https://www.kernel.org
Keywords: acs arbiter assignment gpu i915 kvm override passthrough pci qemu vfio vga
Licenses: GPL-2.0-or-later
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Submitter: zman0900
Maintainer: xiota
Last Packager: xiota
Votes: 73
Popularity: 0.000851
First Submitted: 2015-01-30 06:41 (UTC)
Last Updated: 2024-09-14 07:14 (UTC)

Required by (5)

Sources (7)

Pinned Comments

xiota commented on 2024-01-09 18:43 (UTC) (edited on 2024-01-11 16:53 (UTC) by xiota)

  • 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.

eclairevoyant commented on 2023-04-06 21:24 (UTC) (edited on 2023-04-06 21:31 (UTC) by eclairevoyant)

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

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).

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 32 Next › Last »

slowbro commented on 2020-06-10 03:15 (UTC)

Just threw 5.6.15 up, sorry for the delay. Note that heftig's GPG key was rotated recently, so you'll probably need to gpg --recv-keys 3B94A80E50A477C7 before building.

shaybox commented on 2020-06-10 02:44 (UTC)

5.6.10 Is no longer supported by kernel modules, and 5.7 is testing, at-least update to 5.6.13 for module support so the nvidia drivers work, the current patch-set works with 5.6.13 no change required.

plntyk commented on 2020-05-19 16:06 (UTC)

with gcc 10 i have a compile error on virt/kvm/kvm main.c:2236

it seems upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=207173 should be fixed with 5.7 upstream mentioned there

commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=78a5255ffb6a1

adding that patch makes it compile again

markzz commented on 2020-05-11 06:29 (UTC) (edited on 2020-05-11 06:31 (UTC) by markzz)

It wouldn't matter much anyways because I'm almost certain that X does not support hot plugging display devices. Heck, if you notice in the 0/6 patch, the submitter mentions that he restarts X when hot plugging, which is what I would expect.

The patch seems to be for people who are hotplugging PCI-e devices (which I would expect to be over Thunderbolt), which is something I would bet a vast majority of users do not attempt. I do not expect this patch would improve AMDGPU users' experiences while running a "normal" setup with just a AMD video device plugged directly into one of the available PCI-e slots inside their machines and not touching it while the machine is running (as is a very good idea to not touch an active device on a PCI-e slot/device that isn't specifically designed for hot plugging).

Also, it appears that the issues discussed in the earlier comments are related to certain AMD processors and not video devices.

slowbro commented on 2020-05-11 04:51 (UTC)

I'll admit I don't know much in the ways of DRI or internal kernel workings. There's a patchset that has been penned by Andrey Grodzovsky, a Software Engineer at AMD, that purports to resolve some of these issues. For those using AMDGPU who are experiencing issues, I suggest you read his patch summary, and look into testing these patches on your system(s).

I hope that in the coming days/weeks more detailed information and better patches will be released; it looks like this, at the very least, has the attention of AMD.

https://lists.freedesktop.org/archives/dri-devel/2020-May/265386.html

yankeedoodle commented on 2020-05-08 14:26 (UTC)

QEMU5 update is breaking windows VM's on newer Ryzen processors. Apparently fix is to disable amd-stibp in the cpu flags or use earlier kernel for the moment. Various workarounds in the vfio discord.

meadovv commented on 2020-05-08 14:18 (UTC)

I get the same error as purploid, AMD host GPU, passing down an Nvidia; last kernel update seems to have broken something because switching to LTS fixed it. I'm on x570 chipset if that matters

<deleted-account> commented on 2020-05-08 05:05 (UTC)

markzz: I am not. I am using AMDGPU for my host system and am passing an nvidia card to the guest VM. It's possible there was another change somewhere along the way but this issue popped up after upgrading from 5.6.8 to 5.6.10-1.

I am finding that the LTS kernel doesn't give me this issue. Now that I can boot the Windows guest, the only thing I can see in the minidump file is NTOSKRNL.exe crashing which doesn't give me much to go on and I haven't had any major updates on the guest VM in a while.

markzz commented on 2020-05-08 00:49 (UTC)

purploid: Are you using i915 VGA arbitration?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 32 Next › Last »