Red Hat Bugzilla – Bug 867152
Last modified: 2012-11-01 14:43:29 EDT
Description of problem:
The VFIO userspace device driver interface was added in Linux 3.6 but is not enabled in Fedora. This is true of fc17 and I assume fc18.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2. grep VFIO /boot/config-`uname -r`
# CONFIG_VFIO is not set
Why should we enable this?
Are there any userspace dependencies?
Will it impact how peoples machines (or guests) currently boot?
(In reply to comment #1)
> Why should we enable this?
VFIO is the new mechanism for doing PCI device assignment in Qemu and should eventually supersede and deprecate KVM based device assignment.
> Are there any userspace dependencies?
No, current qemu development branch will use it if available, but depends on it only for vfio-based PCI device assignment.
> Will it impact how peoples machines (or guests) currently boot?
No, there are no devices automatically probed by the driver, it uses a pci-stub approach to only attach to devices explicitly indicated by the sysadmin. The driver is only useful in combination with IOMMU hardware, so it's not useful in guests.
Excellent. Thanks for the info.
I'm guessing you want this in F17, F18, and rawhide.
(In reply to comment #3)
> Excellent. Thanks for the info.
> I'm guessing you want this in F17, F18, and rawhide.
kernel-3.6.3-3.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.6.3-3.fc18'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).