does not support cloning vm storage on lvm backend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Fix Released
|
Low
|
Jamie Strandboge | ||
virt-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
It would appear that libvirt does not support cloning a VM that is using an LVM backend.
Selecting "Clone" presents the user with a dialog prompting for a new name and options for networking and the storage details. However, below the LVM based storage entry is a statement: "Could not determine original disk information: Disk '/dev/group/volume' does not exist." Where /dev/group/volume is the full path to the LVM volume being used by the VM. The referenced device does indeed exist, as it is successfully being used by the VM being cloned.
Searching on this seems to indicate that there were patches provided back in July of '09:
http://<email address hidden>
It would appear that most of the patches were accepted:
http://<email address hidden>
Looks like the version in Lucid (0.7.5) was released several months after those patches were committed (based on the above referenced messages and the upstream release archive).
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: libvirt-bin 0.7.5-5ubuntu27
ProcVersionSign
Uname: Linux 2.6.32-23-server x86_64
Architecture: amd64
Date: Wed Aug 4 11:12:09 2010
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: libvirt
Related branches
Changed in libvirt (Ubuntu): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
status: | Incomplete → Triaged |
Changed in virt-manager (Ubuntu): | |
status: | New → Invalid |
Changed in libvirt (Ubuntu): | |
status: | Incomplete → Triaged |
Changed in libvirt (Ubuntu): | |
status: | Triaged → In Progress |
Jamin,
I suspect this is related to apparmour profile for libvirt. Do you see messages in dmesg after attempting this ?