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

> On 13 Jun 2016, at 11:48, Colin Coe wrote: > > Initially we only saw this on VMs with 2 or more disks. Subsequently we > confirmed that it does happen on single disk VMs also. > Sounds like an issue with snapshots, "backing filename too long” should be

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

Initially we only saw this on VMs with 2 or more disks. Subsequently we confirmed that it does happen on single disk VMs also. CC --- Sent from my Nexus 5 On Jun 13, 2016 5:12 PM, "gregor" wrote: > The VM has two disks both are VirtIO. During testing its now clear that

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

The VM has two disks both are VirtIO. During testing its now clear that the problem occur only with two disks. When I select only one disk for the snapshost it works. Is this a problem of oVirt or is it not possible to use two disks on a VM in oVirt? Have you also two or more disks on your VM?

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

Yeah, that looks like the fix Red Hat GSS came up with. Note that is only online snapshots that we've seen the problem with, never offline but YMMV. What version of oVirt are you running? We're running RHEV 3.5.7 in prod and test environments but 3.6.5 in dev and we've not had a re-occurrence

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

Hi, I solved my problem, here are the steps but be carefully if you don't know what the commands did and how to restore from backup don't follow this: - ssh to the host - systemctl stop ovirt-engine - backup the database with "engine-backup" - navigate to the image files - backup the images:

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

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

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

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 of problems. Which OS you used on the problematic VM? cheers gregor On 11/06/16