Bug 1000051 - Support only vfio-based device assignment
Summary: Support only vfio-based device assignment
Keywords:
Status: CLOSED DUPLICATE of bug 1025880
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Alex Williamson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1000056 1025880
Blocks: 720747
TreeView+ depends on / blocked
 
Reported: 2013-08-22 14:53 UTC by Alex Williamson
Modified: 2013-12-04 16:26 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-04 16:26:26 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Alex Williamson 2013-08-22 14:53:23 UTC 
Description of problem:
legacy KVM device assignment is deprecated.  Support only vfio-based device assignment going forward.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Ademar Reis 2013-11-05 21:47:02 UTC 
I got this from Markus: "As far as I know, the plan is to disable legacy KVM device in the *kernel*, and then close this bug without patching qemu-kvm."

Alex: is that your understanding as well?
Comment 3 Alex Williamson 2013-11-05 22:10:04 UTC 
(In reply to Ademar de Souza Reis Jr. from comment #2)
> I got this from Markus: "As far as I know, the plan is to disable legacy KVM
> device in the *kernel*, and then close this bug without patching qemu-kvm."
> 
> Alex: is that your understanding as well?

Yes, pci-assign should fail gracefully in qemu when it's disabled in the kernel.  libvirt should also favor vfio when configuring a guest, so the only way a user would be exposed to it is to manually configure their guest xml for pci-assign.  We would only need to patch qemu if exposing the pci-assign driver but not having it work is somehow unacceptable.
Comment 4 Alex Williamson 2013-12-04 16:26:26 UTC 

*** This bug has been marked as a duplicate of bug 1025880 ***
Note You need to log in before you can comment on or make changes to this bug.