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 740686 - virsh nodedev-* commands are undocumented
Summary: virsh nodedev-* commands are undocumented
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Eric Blake
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 736437
TreeView+ depends on / blocked
 
Reported: 2011-09-22 22:56 UTC by Eric Blake
Modified: 2011-12-06 11:34 UTC (History)
12 users (show)

Fixed In Version: libvirt-0.9.4-14.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 736437
Environment:
Last Closed: 2011-12-06 11:34:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1513 0 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2011-12-06 01:23:30 UTC

Comment 1 Eric Blake 2011-09-22 22:58:18 UTC
This bug exists to track the fact that nodedev-* commands of virsh are completely undocumented, including the fact that nodedev-reattach must be used to give a pci passthrough device back to the host after it is no longer needed by any guests.

Comment 6 Vivian Bian 2011-09-29 06:11:46 UTC
tested with 
libvirt-0.9.4-13.el6.x86_64
libvirt-0.9.4-14.el6.x86_64

man virsh 
in -13 build ,there is no nodedev doc, and in -14, nodedev doc is added. Checked libvirt.org, Node devices XML format page has been created under Documentation -> XML format -> Node Devices . 

All of the patch has streamed into -14 build . So set bug status to VERIFIED

Comment 11 yuping zhang 2011-11-03 03:16:23 UTC
Verified the new patch with libvirt-0.9.4-21.el6.x86_64.

Domain XML format page has been updated under Documentation -> XML format -> Domains: 
...
"and reattached to the host after the guest exits. If managed is omitted or "no", and for USB devices, the user is responsible to call virNodeDeviceDettach (or virsh nodedev-dettach) before starting the guest or hot-plugging the device, and virNodeDeviceReAttach (or virsh nodedev-reattach) after hot-unplug or stopping the guest."

And in virsh manual,all content in patch has been updated.

Comment 12 errata-xmlrpc 2011-12-06 11:34:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1513.html


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