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.
DescriptionDirect Docs Feedback
2021-09-10 16:08:20 UTC
11.3.6. Creating LVM-based storage pools using the CLI
This part is very confusing for me and lead to issues.
In this section - for 'logical' pools the command
# virsh pool-build ...
is not listed.
This leads to an error if the 'source' (libvirt_lvm) doesn't exist.
error: Failed to start pool guest_images_logical
error: unsupported configuration: cannot find logical volume group name 'libvirt_lvm'
The doc says:
"that uses a libvirt_lvm LVM device mounted on /dev/sdc"
IIUC, this is not correct. Supposing that here you mean the volume group already exists and doesn't have to be created this might better read:
"that uses an existing pysical volume /dev/sdc inside of the volume group libvirt_vm". At least, that's how I understand it.
Reported by: smitterl
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/managing-storage-for-virtual-machines_configuring-and-managing-virtualization#annotations:46c44938-eebd-4daf-93d2-a1759a72df2c
Verified with:
libvirt-7.6.0-5.module+el8.5.0+12933+58cb48a1.s390x
Note:
The doc supposes vg has already been set up. I tested with vg on DASD partition using cdl layout and single parition (fdasd -a).