Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionDon Dutile (Red Hat)
2011-09-09 16:17:14 UTC
Description of problem:
(1) Looking at the table of contents, and trying to find virsh command line help is a bit like finding a needle in a haystack.
Ch 15, Managing Guests with virsh, should have section numbers prefixing most of the topic headers.
For example:
'virsh command quick reference' should be tagged as 15.1,
'Attaching and updating a device with virsh' should be tagged as 15.2
Will update this bz in a comment with recommended section numbering, naming, and what existing content should be pulled under those sections.
(2) another set of virsh capability has been brought to my attention that receives a significant amount of email and that is cpu model & features definition for a guest. A new section titled 'Guest CPU model configuration' should be added. Content for the new section will be added as an attachment.
The source of the content will come from this web link, edited for RHEL6 and this document:
http://berrange.com/posts/2010/02/15/guest-cpu-model-configuration-in-libvirt-with-qemukvm/
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 2Don Dutile (Red Hat)
2011-09-09 20:51:57 UTC
Created attachment 522403[details]
New section describing guest cpu model configuration
Added txt file containing new content for chapter 15,
'Guest CPU model configuraton'
Comment 3Don Dutile (Red Hat)
2011-09-09 21:53:00 UTC
Suggested section numbering & titling for chapter 15:
15.1 virsh command quick reference
15.2 Attaching and updating a device with virsh
15.3 Connecting to the hypervisor
*NOTE*: should add command 'virsh uri' to get value to put into {name}
for virsh connect
15.4 Creating a virtual machine XML configuration file
dump xml
creating a guest from...
editing a guest's configuration file
15.5 Suspending, resume, saving, & restoring a guest
15.6 shutting down, rebooting, force-shutdown of a guest
15.7 Guest information
virsh domname
virsh domuuid
virsh dominfo
15.8 host information
virsh capabilities <-- *NEW*; lead in for new section provided in c#2
virsh nodeinfo
15.9 storage pool information
virsh pool-edit
15.9 Displaying per-guest information
virsh list
virsh vcpuinfo
virsh vcpupin
virsh setvcpus <-- supported on KVM ????
virsh setmem
virsh domblkstat
virsh domifstat
15.10 Managing virtual networks
15.11 Migrating a guest
virsh migrate
15.12 <new content in c#2>