RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 603867 - libvirt: VM startup fails trying to resolve 'usbX' format sysfs files
Summary: libvirt: VM startup fails trying to resolve 'usbX' format sysfs files
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-14 18:01 UTC by Cole Robinson
Modified: 2010-11-11 14:49 UTC (History)
5 users (show)

Fixed In Version: libvirt-0_8_1-11_el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-11 14:49:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Backport of upstream fix (1.13 KB, text/plain)
2010-06-25 16:31 UTC, Cole Robinson
no flags Details

Description Cole Robinson 2010-06-14 18:01:58 UTC
Some files under /sys/bus/usb/devices/ have the format 'usbX', where
X is the USB bus number. Libvirt doesn't properly parse these files when trying to resolve produce/vendor to bus/device info. When it can't parse, the guest won't start. See also Fedora bug https://bugzilla.redhat.com/show_bug.cgi?id=598272

Fixed upstream here, should be a simple backport:

http://libvirt.org/git/?p=libvirt.git;a=commit;h=fa6da6608abb262cbbe3d200bd989c17c6409090

Comment 1 RHEL Program Management 2010-06-14 18:02:59 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 2 Cole Robinson 2010-06-25 16:31:33 UTC
Created attachment 426927 [details]
Backport of upstream fix

Internal posting:

http://post-office.corp.redhat.com/archives/rhvirt-patches/2010-June/msg00984.html

Comment 3 Dave Allan 2010-06-29 03:00:04 UTC
libvirt-0_8_1-11_el6 has been built in RHEL-6-candidate with the fix.

Dave

Comment 4 dyuan 2010-07-01 10:40:13 UTC
Verified PASSED with libvirt-0.8.1-13.el6.

VM start successfully with the following line in xml.
# virsh dumpxml demo
[...]
<hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0x1d6b'/>
        <product id='0x0002'/>
        <address bus='1' device='1'/>
      </source>
      <alias name='hostdev0'/>
    </hostdev>

[...]

Comment 5 releng-rhel@redhat.com 2010-11-11 14:49:19 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.