----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>
To: "Alissa Bonas" <abonas(a)redhat.com>
Cc: "users" <users(a)ovirt.org>
Sent: Tuesday, March 5, 2013 5:31:19 PM
Subject: Re: [Users] clone vm from snapshot problem in 3.2
On Tue, Mar 5, 2013 at 1:48 PM, Alissa Bonas wrote:
> Thanks for additional information.
> The engine log actually shows that slclone started ok:
> "VM slclone c6c56d41-d70d-4b9b-a1cb-8b0c097b89a0 moved from
> PoweringUp --> Up"
> Can you explain what problem are you experiencing in that VM?
> Also, could provide the vdsm log from the same timeframe?
The Vm doesn't boot.
As I wrote in the other e-mail:
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...
What is important here is to check the boot properties of both devices as
they are configured for the master and clone.
They might not be swapped, the order in the console is not necessarily the issue here.
Please attach vdsm.log with times of both machines boot. the properties of the devices
boot should be part of the startup command so it should help to investigate the issue.