Sound's bad. Recreating the VM is no way because this is a productive
VM. During testing I need to recreate it more than once. oVirt works
perfect which Linux VM's but when it comes to Windows VM's we get lots
Which OS you used on the problematic VM?
On 11/06/16 19:22, Anantha Raghava wrote:
Even I observed this behaviour.
When we take the snapshot, the main VM using which the snapshot was
taken is shutdown and a new VM with external-<VMName> comes to life. We
cannot get the original VM back to life, but a clone starts functioning.
We cannot remove the snapshot whether or not the VM is running. I had to
remove the entire VM that came to life with snapshot and recreate the
entire VM from scratch. Luckily the VM was still not in production,
hence could afford it.
First I could not understand, why, when a snapshot is created, the VM
with snapshot comes to life and starts running and not the original VM.
Is it necessary that we shutdown the VM before taking snapshots?
Snapshot is supposed to be a backup of original VM, that unless we
restore by cloning should not come to life as I understand.
Thanks & Regards,
On Saturday 11 June 2016 08:09 PM, gregor wrote:
> a VM has snapshots which are unable to remove during when the VM is up.
> Therefore I power down the Windows Server 2012 VM. The snapshots are
> still unable to remove and the VM can't boot anymore !!!
> This is the message from engine.log
> Message: VM srv03 is down with error. Exit message: Bad volume specification
> Clone is not possible I get:
> Message: VDSM command failed: Image is not a legal chain
> All others VM's can be powered down and start without any problem.
> What can I do?
> This is very important because now no one can work :-( !!!
> Users mailing list