| Summary: | libvirt does not properly probe for vfio support | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alex Williamson <alex.williamson> |
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
| Status: | CLOSED DEFERRED | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | berrange, clalancette, crobinso, itamar, jforbes, laine, libvirt-maint, veillard, virt-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-16 23:31:48 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Alex Williamson
2013-11-13 01:35:21 UTC
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 |