Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1497984

Summary:	RFE: support addressing USB host devices by port
Product:	Red Hat Enterprise Linux Advanced Virtualization	Reporter:	Daniel Berrangé <berrange>
Component:	libvirt	Assignee:	Virtualization Maintenance <virt-maint>
Status:	CLOSED WONTFIX	QA Contact:	lijuan men <lmen>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	dyuan, jsuchane, lersek, lmen, rbalakri, xuzhang
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	8.0	Flags:	areis: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-15 07:43:00 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Berrangé 2017-10-03 09:40:35 UTC

Description of problem:
Currently when assigning a host USB device to a guest you must specify the bus + device numbers, or using a vendor+product ID pair. Both of these approaches are flawed in their own way:

* Device numbers are not stable. Every time you plug+unplug the device the device number is incremented by one. So effectively the device number is only useful with transient guests - if using in a persistent guest config it will likely fail in the future
* Vendor + product ID pairs are not unique if two or more identical devices are attached.

Fortunately QEMU does now provide an alternative which is to address the host device based on a bus + port number pair. This is guaranteed unique and stable for as long as the device is plugged into the same physical port. This is clearly the most useful addressing method for persistent guests and libvirt should support it

There was a patch for this sent upstream but we dropped the ball & never reviewed or merged it

https://www.redhat.com/archives/libvir-list/2016-July/msg00127.html

Comment 5 RHEL Program Management 2021-01-15 07:43:00 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.