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

Bug 1575824

Summary:	Unusual naming for USB devices
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Germano Veit Michel <gveitmic>
Component:	ovirt-engine	Assignee:	Nobody <nobody>
Status:	CLOSED WONTFIX	QA Contact:	meital avital <mavital>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.2.2	CC:	lsurette, michal.skrivanek, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-08 06:35:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1511234

Description Germano Veit Michel 2018-05-08 03:51:53 UTC

Description of problem:

The naming for USB hostdev differs from other device types.

Example:
usb hostdev from 'bus=1 device=1' -> name: usb_usb1
usb hostdev from 'bus=3 device=6' -> name: usb_3_6

So if the bus is 1, the device is named usb_usbX. If the bus is not 1, it is named usb_X_Y. Not sure if there are other variants.

Why not use usb_X_Y structure like the other hostdev devices like pci and scsi?

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.2.6-1.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
1. Add a USB hostdev from bus 1 to a VM
2. Add a USB hostdev from bus != 1 to a VM
3. Check the names of the devices in the 'Host Devices' tab of the VM.

Actual results:
Inconsistent naming

Expected results:
Consistent naming

Additional information:
IIUC, buildVmUsbSlots() has always been like this, always adding USB_BUS.

Comment 1 Michal Skrivanek 2018-05-08 06:35:46 UTC

That's internal naming we get from libvirt. usb_usb1 is the root hub and usb_1_X are devices in it. Nothing we can control

In 4.2 when running on el7.5 you'll get device aliases for consistent unique identification of devices if needed

Comment 2 Germano Veit Michel 2018-05-08 07:03:38 UTC

Got it, thanks Michal!

Comment 3 Franta Kust 2019-05-16 13:05:00 UTC

BZ<2>Jira Resync