Description of problem: qemuHostdevHostSupportsPassthroughVFIO checks for /dev/vfio/vfio, but vfio is built as a module and libvirt makes no attempt to load it. Version-Release number of selected component (if applicable): 1.1.4-2.fc20 (virt-preview) How reproducible: 100% Steps to Reproduce: 1. unload all vfio modules 2. attempt to assign a device, in my case both functions of a two function device 3. Actual results: error: Failed to start domain xxxxxxxx error: internal error: Unable to reset PCI device 0000:04:00.0: internal error: Active 0000:04:00.1 devices on bus with 0000:04:00.0, not doing bus reset Expected results: libvirt loads modules and works Additional info: If I 'modprobe vfio' then /dev/vfio/vfio is created and libvirt will load the vfio-pci module, attach devices, and start the domain correctly.
What you're requesting isn't just "probing for vfio support", it's modifying the system configuration. If someone wants to specifically disable vfio on their system, that's their choice, not libvirt's, and libvirt shouldn't try to override that choice. Beyond that, if VFIO is going to be the default on any given version of any distro, then the default system config of that distro should be loading the vfio module.
(In reply to Laine Stump from comment #1) > What you're requesting isn't just "probing for vfio support", it's modifying > the system configuration. If someone wants to specifically disable vfio on > their system, that's their choice, not libvirt's, and libvirt shouldn't try > to override that choice. > > Beyond that, if VFIO is going to be the default on any given version of any > distro, then the default system config of that distro should be loading the > vfio module. So you would suggest that this is a qemu-kvm issue, that it should include a directive to load vfio just as it already has for kvm and vhost-net?
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
(In reply to Alex Williamson from comment #2) > (In reply to Laine Stump from comment #1) > > What you're requesting isn't just "probing for vfio support", it's modifying > > the system configuration. If someone wants to specifically disable vfio on > > their system, that's their choice, not libvirt's, and libvirt shouldn't try > > to override that choice. > > > > Beyond that, if VFIO is going to be the default on any given version of any > > distro, then the default system config of that distro should be loading the > > vfio module. > > So you would suggest that this is a qemu-kvm issue, that it should include a > directive to load vfio just as it already has for kvm and vhost-net? Not sure if you ever went this route, but it's probably the best thing to do... libvirt doesn't mess with loading modules so it's simplest to stick to that pattern