Created attachment 316463 [details]
Description of problem:
Attempting to add an LVM VolGroup is not clear. It appears like the dialog is not allowing me to enter a the volume group. Perhaps tooltips or documentation might be in order.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start virt-manager
2. Select 'Details' for QEMU localhost
3. Select 'Storage Pools' tab
4. Select 'Add'
5. Select type=logical, name=VolGroup00, select Next
6. Select Next
Clicking next yields ...
[Wed, 24 Sep 2008 15:37:26 virt-manager 22506] DEBUG (Storage:370) Creating storage pool 'VolGroup00' with xml:
[Wed, 24 Sep 2008 15:37:26 virt-manager 22506] ERROR (createpool:297) Error creating pool: Could not define storage pool: cannot extract storage pool source devices
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/createpool.py", line 291, in _async_pool_create
poolobj = self._pool.install(create=True, meter=meter, build=build)
File "/usr/lib/python2.5/site-packages/virtinst/Storage.py", line 375, in install
raise RuntimeError(_("Could not define storage pool: %s" % str(e)))
RuntimeError: Could not define storage pool: cannot extract storage pool source devices
* it doesn't appear possible to enter a LVM Volume Group name for use with the storage pool
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Re-assigning to virt-manager for now, because from my testing, the libvirt side of things is working OK.
If I understand correctly, the root of this issue is that the storage pool 'name' for an LVM pool is used as the source VG name, if no source name is specified (if creating a pool from an existing VG). This is confusing, since for all other storage pool types, 'name' is strictly metadata.
We should really be using the logical pool discovery functionality to provide a list of volume groups to the user: we can use this info to specify the 'source' device name. Granted, it would be nice if libvirt did this behind the scenes if no source name is specified, but we need to implement this functionality in virt-manager regardless.
This likely won't be fixed for F10, moving to F11.
We now support pool enumeration upstream:
This requires changes across virtinst and virt-manager, so I don't think this will be backported to F11. Moving to rawhide/F12
This should be fixed in virt-manager-0.8.1-1.fc13 which will be in the next rawhide compose.