[ovirt-users] Can't start VM after shutdown

[gregor]

Thanks for sharing the information's, I check the file structure and
database entries. I had problems with too long names during coding a
oVirt backup tool [1]. Here is a limitations list [2]. There was the
problem that a Windows VM name can only be 15 characters long, others
can named with 64 characters.

Which OS you used on the problematic VM?

cheers
gregor

[1] https://github.com/wefixit-AT/oVirtBackup
[2]
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.2/html/Administration_Guide/Red_Hat_Enterprise_Virtualization_Manager_configuration_options_explanations_limitations_and_best_practices.html

On 12/06/16 02:16, Colin Coe wrote:
> We had the same problem. Turned out that qemu-img was complaining that
> the image file was too long. We use RHEV and Red Hat support did the
> hard work to correct the image chain.  Its quite a process...
> 
> CC
> 
> On Sat, Jun 11, 2016 at 10:39 PM, gregor <gregor_forum at catrix.at
> <mailto:gregor_forum at catrix.at>> wrote:
> 
>     Hi,
> 
>     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 :-( !!!
> 
>     cheers
>     gregor
>     _______________________________________________
>     Users mailing list
>     Users at ovirt.org <mailto:Users at ovirt.org>
>     http://lists.ovirt.org/mailman/listinfo/users
> 
>