Red Hat Bugzilla – Bug 866481
lvcreate with allocation=0 fails, which virt-manager does by default
Last modified: 2012-12-13 11:59:15 EST
Description of problem:
When I want to create new storage volume in my pool (which is LVM volume groups) the following error occurs and no volume is created (creating of the storage volume on filesystem works fine):
Error creating vol: internal error Child process (/usr/sbin/lvchange -aln vg_data/newlv) unexpected exit status 5: One or more specified logical volume(s) not found.
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/createvol.py", line 248, in _async_vol_create
File "/usr/lib/python2.7/site-packages/virtinst/Storage.py", line 1213, in install
vol = self.pool.createXML(xml, 0)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2262, in createXML
if ret is None:raise libvirtError('virStorageVolCreateXML() failed', pool=self)
libvirtError: internal error Child process (/usr/sbin/lvchange -aln vg_data/newlv) unexpected exit status 5: One or more specified logical volume(s) not found.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to create a new storage volume in lvm volume group pool
Error message is shown and no volume is created
New volume should be created
I propose this bug as final blocker. User won't be able to create a new virtual machine (with LVM vg pool), so he/she won't be able to host the system. Violated criterion is: "The release must be able host virtual guest instances of the same release, using Fedora's current preferred virtualization technology"
I wouldn't call this a blocked: while LVM is the preferred and default storage for the host machine, most people don't use it to provision virt storage on the host, and it's not the default virt-manager config.
Also it's quite easy to work around: just set a non-zero 'allocation' in the UI.
The root issue here is that lvcreate doesn't like allocation=0 which is what virt-manager obviously does by default. I think this is really a libvirt issue, it can easily turn 0 into a minimal value to make lvcreate happy and still give API users the closest approximation to what they requested.
I've sent a libvirt patch upstream that fixes this:
libvirt-0.10.2.1-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libvirt-0.10.2.1-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
libvirt-0.10.2.1-2.fc18 has been submitted as an update for Fedora 18.
The update was pushed stable, closing (Bodhi was broken for a while, this is me doing my Bodhi impersonation). Petr, do re-open if this is not actually fixed.
*** Bug 872162 has been marked as a duplicate of this bug. ***