RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1055225 - Cannot clone a logical volume based VM via virt-manager even if the volume is fully allocated
Summary: Cannot clone a logical volume based VM via virt-manager even if the volume is...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: python-virtinst
Version: 6.5
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Giuseppe Scrivano
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 1060021 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-19 16:40 UTC by John Blaut
Modified: 2018-12-09 17:26 UTC (History)
8 users (show)

Fixed In Version: python-virtinst-0.600.0-21.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-14 06:24:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1444 0 normal SHIPPED_LIVE python-virtinst bug fix and enhancement update 2014-10-14 01:05:50 UTC

Description John Blaut 2014-01-19 16:40:44 UTC 
Description of problem:

When trying to clone a KVM virtual machine in EL 6.5 whose virtual disk is a logical volume, using the virt-manager 'Clone' button, this fails with the following type of error: "Sparse logical volumes are not supported". 

I suppose the latter is being enforced as a result of the resolution for previous bug: 921480 

However kindly note that the logical volumes we are using, are not sparse, but fully allocated, so they should be supported.

You may reproduce this problem in EL 6.5 with the following packages installed:
virt-manager-0.9.0-19.el6.x86_64
python-virtinst-0.600.0-18.el6.noarch

In order to work around this issue, I had to revert to the previous versions of both the virt-manager and python-virtinst packages as found in EL 6.4:
virt-manager-0.9.0-18.el6.x86_64
python-virtinst-0.600.0-15.el6.noarch

Since we intentionally tend to always use fully allocated logical volumes anyway, we can live without the latest virt-manager/python-virtinst which explicitly warn/protect against the use of sparse logical volumes. 

However, it would be ideal that the latest version would also support again cloning of VMs using the 'Clone' button, when the logical volumes are indeed not sparse as opposed to what virt-manager/python-virtinst claims. This way we do not need to keep track of excluded packages when installing updates.
Comment 3 Giuseppe Scrivano 2014-01-31 23:45:29 UTC 
*** Bug 1060021 has been marked as a duplicate of this bug. ***
Comment 4 zhengqin 2014-02-19 05:34:26 UTC 
I could reproduce this issue on latest rhel6.5 with virt-manager-0.9.0-18.el6.x86_64.


Reproduce steps:
1. Create a guest which created by lvm disk image
2. Try to clone it by virt-manager, will fails with the following type of error: "Sparse logical volumes are not supported". 


This issue does NOT occur on RHEL7
Comment 6 tingting zheng 2014-05-04 07:44:52 UTC 
Tested the bug with:
python-virtinst-0.600.0-20.el6.noarch
virt-manager-0.9.0-20.el6.x86_64

Steps:
1. Create a guest with a fully allocated lvm disk image,in my case it is '/dev/vgtest/sd-clone'
2. Try to clone it by virt-manager, after click "Clone",error shows:
Error setting clone parameters: Could not use path '/dev/vgtest/sd-clone' for cloning: Sparse logical volumes are not supported, allocation must be equal to capacity

Error setting clone parameters: Could not use path '/dev/vgtest/sd-clone' for cloning: Sparse logical volumes are not supported, allocation must be equal to capacity

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 853, in _do_show_clone
    clone_window.show(src.topwin)
  File "/usr/share/virt-manager/virtManager/clone.py", line 180, in show
    self.reset_state()
  File "/usr/share/virt-manager/virtManager/clone.py", line 249, in reset_state
    self.populate_storage_lists()
  File "/usr/share/virt-manager/virtManager/clone.py", line 583, in populate_storage_lists
    self.clone_design.clone_devices = new_disks
  File "/usr/lib/python2.6/site-packages/virtinst/CloneManager.py", line 232, in set_clone_devices
    (path, str(e)))
ValueError: Could not use path '/dev/vgtest/sd-clone' for cloning: Sparse logical volumes are not supported, allocation must be equal to capacity

Refer to the above comments,move the bug back to ASSIGNED.
Comment 9 tingting zheng 2014-05-07 08:09:12 UTC 
Tested with:
python-virtinst-0.600.0-21.el6.noarch
virt-manager-0.9.0-21.el6.x86_64

Steps:
1. Create a guest with a fully allocated lvm disk image,in my case it is '/dev/vgtest/sd'
2. Try to clone it by virt-manager, click "Clone",the guest can be cloned successfully without any error.

Refer to the above comments,move the bug to VERIFIED.
Comment 10 errata-xmlrpc 2014-10-14 06:24:04 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1444.html
Note You need to log in before you can comment on or make changes to this bug.