From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>
To: "Liron Aravot" <laravot(a)redhat.com>
Cc: "users" <users(a)ovirt.org>, "Vered Volansky"
Sent: Thursday, February 28, 2013 7:07:55 PM
Subject: Re: [Users] clone vm from snapshot problem in 3.2
On Wed, Feb 27, 2013 at 1:21 PM, Liron Aravot wrote:
>> Hi Gianluca,
>> I've built 3.2 and had success in reproducing your issue, I've
>> tested the fix and after it the clone window shows fine - so this
>> should solve your issue (http://gerrit.ovirt.org/#/c/11254/
>> Thanks, Liron.
so I rebuilt with the patch.
I built as in this thread:
directly on engine server and with engine stopped:
sudo rpm -Uvh --force $(ls -1|grep -v all)
$ ls -1|grep -v all
and then reboot the engine
OK, for the snapshot details pane. It seem the patch fixes this too.
Until now I was never able to see snapshot details,
Instead now I can see disk and nic details. See:
OK, if I clone a VM from a snapshot of a running VM (CentOS 5.6)
I start the clone and no problem at all.
Corner cases and problems
OK, if I clone a powered on VM from a snapshot with two disks and
you can find clone in action with webadmin gui and iotop on node that
shows they are cloning in parallel.. well!
The VM is a slackware 14 32bit with virtio disk that I obtained from
virt-v2v from CentOS 6.3+Qemu/KVM
The problem is that the cloned VM recognizes the disks in reversed
See these images where sl1432 is master slcone is the clone
disk layout in details pane seems equal with boot disk the one that
appears as the second, but the master boots ok, the slave no.
Disks are swapped
Master VM disk details:
Clone VM disks details:
Page with the two consoles where you can see that vda of master
becomes vdb of clone and vice-versa:
Can I swap again in some way? In VMware for example you can see and
edit SCSI IDs of disks...
KO, if I clone a windows 7 VM from a snapshot (time 17:09) I get this
You can find the engine.log from server restart (at 17:06) here:
Are there any restrictions?
The VM was powered off when taking the snapshot and making the clone.
Regarding the second item you mentioned - failure of the clone vm from snapshot,
the engine log indicates that the following error occurred "Volume Group not big
enough" - suggesting you might check if you have enough free space.
Users mailing list