Bug 2003216

Summary:	[DDF] 11.3.6. Creating LVM-based storage pools using the CLI
Product:	Red Hat Enterprise Linux 8	Reporter:	Direct Docs Feedback <ddf-bot>
Component:	Documentation	Assignee:	bbrezani
Documentation sub component:	DDF	QA Contact:	smitterl
Status:	CLOSED CURRENTRELEASE	Docs Contact:	bbrezani
Severity:	unspecified
Priority:	medium	CC:	bbrezani, rhel-docs, smitterl
Version:	8.0	Keywords:	Documentation
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-01 16:15:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Direct 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

Comment 4 smitterl 2021-10-27 11:57:34 UTC

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).

Comment 5 bbrezani 2021-11-01 16:15:42 UTC

The procedure was modified to describe using an existing volume group:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_virtualization/index#creating-lvm-based-storage-pools-using-the-cli_creating-storage-for-virtual-machines-using-the-cli