Bug 714431

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):
libvirt-bin                         0.8.3-5+squeeze1
libvirt0                            0.8.3-5+squeeze1 
python-libvirt                      0.8.3-5+squeeze1 
virt-manager                        0.8.4-8

How reproducible:
always

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
6. continue
  
Actual results:
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"

Expected results:
normal continuation of the VM setup process

Additional info:
The error message by libvirt is correct as you can see here:
 ls /dev/vg1
 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