Bug 1309229

Summary:	RFC: domain: support assigning PCI hostdev via PCI ID
Product:	[Community] Virtualization Tools	Reporter:	Dr. David Alan Gilbert <dgilbert>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	berrange, crobinso, dyuan
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:	2020-04-17 12:26:44 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 Dr. David Alan Gilbert 2016-02-17 09:54:54 UTC

Description of problem:
(This was a request that came out of a discussion with a user at an Openstack meeting)
https://libvirt.org/formatdomain.html#elementsHostDevSubsys states that
    'PCI devices can only be described by their address'
this request is to allow PCI assignment based on ID in the same way (and same syntax?) as used by USB devices. In the case of this user they have a pool of machines with devices in, but they're not all in the same host slot/bridge configuration, so they just want to be able to specify in the XML that the machine must start with a given PCI device ID and let something figure out which one to use.

(The user actually wanted to be able to migrate with this in place and was happy for the guest to see a failure of the device during the migrate; that's probably a whole separate story - but the basic request to assign a device with ID seems sensible to me)

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Daniel Berrangé 2020-04-17 12:26:44 UTC

Closing old RFE since we're unlikely to implement this, as we tend to leave such policy decisions to mgmt apps. Especially in the case of OpenStack they want strict control over exactly which device is picked, so it is unlikely they'd use such a feature.