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 713922 - virsh man page refers to unspecified "documentation"
Summary: virsh man page refers to unspecified "documentation"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.2
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Dave Allan
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 747667 756082
TreeView+ depends on / blocked
 
Reported: 2011-06-16 19:11 UTC by Dave Allan
Modified: 2016-04-26 14:09 UTC (History)
5 users (show)

Fixed In Version: libvirt-0.9.13-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 07:06:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0276 0 normal SHIPPED_LIVE Moderate: libvirt security, bug fix, and enhancement update 2013-02-20 21:18:26 UTC

Description Dave Allan 2011-06-16 19:11:45 UTC 
In many places the virsh man page refers the user to "the documentation" but does not provide any guidance as to where that documentation might be found, which is especially puzzling since the man page is itself documentation.  For example:

"See the documentation to learn about libvirt XML format for a device."

In other places, the man page refers the user to a specific webpage:

"To better understand the values allowed as options for the command reading the documentation at <http://libvirt.org/formatdomain.html> on the format of the device sections to get the most accurate set of accepted values."

The man page should specify the webpage in each instance.
Comment 5 Dave Allan 2012-02-27 22:58:56 UTC 
Sent patch upstream.
Comment 6 Dave Allan 2012-03-22 02:16:00 UTC 
Sent v2 upstream:

http://www.redhat.com/archives/libvir-list/2012-March/msg00907.html
Comment 9 Dave Allan 2012-05-10 16:34:34 UTC 
Upstream commit:

commit ceb1d36b94be1de7264f86d1490450237238dc30
Author: Dave Allan <dallan>
Date:   Wed Mar 21 22:07:51 2012 -0400

    Clarify what documentation is being referenced
    
    virsh.pod had several instances in which it referred to "the
    documentation" which was a little puzzling to me since it is
    documentation.  Reading the document from end to end makes it clear
    that it means a specific URI which was noted previously in the text,
    but I had never noticed those URIs in several years of referring to
    the man page.  This patch adds those URIs to several additional places
    in the text.
Comment 13 yuping zhang 2012-07-24 11:27:41 UTC 
Verified this issue with libvirt-0.9.13-3.el6.x86_64.

#man virsh
-d, --debug LEVEL
           Enable debug messages at integer LEVEL and above.  LEVEL can range from 0 to 4 (default).  See the documentation of VIRSH_DEBUG environment variable below for the description of each LEVEL. #########updated to "below"

connect URI [--readonly]
	...
	For remote access see the documentation page at <http://libvirt.org/uri.html> on how to make URIs.  The --readonly option allows for read-only connection   ##########link was added

attach-device domain-id FILE [--config]
           Attach a device to the domain, using a device definition in an XML file using a device definition element such as <disk> or <interface> as the top-level element.  See the documentation at <http://libvirt.org/formatdomain.html#elementsDevices> to learn about libvirt XML format for a device. ###############link was added

update-device domain-id file [--config] [--force]
           Update the characteristics of a device associated with domain-id, based on the device definition in an XML file.  If the --config option is used, the changes will take affect the next time libvirt starts the domain.  For compatibility purposes, --persistent is alias of --config.  The --force option can be used to force device update, e.g., to eject a CD-ROM even if it is locked/mounted in the domain. See the documentation at <http://libvirt.org/formatdomain.html#elementsDevices> to learn about libvirt XML format for a device.              ##################link was added

 net-create file
           Create a virtual network from an XML file, see the documentation at
 <http://libvirt.org/formatnetwork.html> to get a description of the XML network format used by libvirt. ##############link was added.

So change the bug status to VERIFEID.
Comment 14 errata-xmlrpc 2013-02-21 07:06:38 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/RHSA-2013-0276.html
Note You need to log in before you can comment on or make changes to this bug.