Red Hat Bugzilla – Bug 714431
Empty LVM volume group leads to side effects on storage pools
Last modified: 2012-01-24 20:40:51 EST
Description of problem:
One or more empty LVM volume groups (read: no logical volumes inside) lead to side effects on other storage pools and VM creation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a local or remote connection to a QEMU/KVM instance in virt-manager
2. Under "details -> storage" add an existing LVM volume group, e.g. "vg1" with path "/dev/vg1" selected from the dropdown. Make sure, the volume group contains no LVs
3. Make sure you have an ISO image accessible in a storage pool of type "dir"
4. Create a new VM named "test" with "local install media (iso-image or cdrom)"
5. Choose "use iso image" and browse to an image in the dir-storage
virt-manager fails with "Checking installer location failed: Could not find media '/var/images/debian-6.0.0-amd64-netinst.iso'."
libvirt logs "error : virStorageBackendStablePath:1279 : cannot read dir '/dev/vg1': No such file or directory"
normal continuation of the VM setup process
The error message by libvirt is correct as you can see here:
ls: cannot access /dev/vg1: No such file or directory
The path is only created on first LV creation.
But I see no reason why this should affect the other storage-pools
*** This bug has been marked as a duplicate of bug 782261 ***