[ovirt-users] Re: Update to 4.2.5, Cant start VMs

2018-08-07 Thread Vincent Royer
Indeed the Storage domains are via NFS served by Windows Server 2016. the workaround says "use NFSV3", I'm afraid this will break my existing installation. For now, all my VMs are running on one host that is still on 4.2.0. On Tue, Aug 7, 2018 at 2:35 PM Stefano Bovina wrote: > I don't know

[ovirt-users] Re: Update to 4.2.5, Cant start VMs

2018-08-07 Thread Raz Tamir
Adding Arik On Tue, Aug 7, 2018, 23:15 Vincent Royer wrote: > Would be great to get some help with this, no VMs will start on a freshly > installed 4.2.5 node (not upgraded, installed fresh from new ISO) > > I created a new VM from Centos 7 template imported from Glance repository. > It won't st

[ovirt-users] Re: Update to 4.2.5, Cant start VMs

2018-08-07 Thread Greg Sheremeta
I see that the bug is urgent but sitting a month. cc'ing some people who may be able to assist. On Tue, Aug 7, 2018 at 4:16 PM Vincent Royer wrote: > Would be great to get some help with this, no VMs will start on a freshly > installed 4.2.5 node (not upgraded, installed fresh from new ISO) > >

[ovirt-users] Re: Update to 4.2.5, Cant start VMs

2018-08-07 Thread Vincent Royer
Would be great to get some help with this, no VMs will start on a freshly installed 4.2.5 node (not upgraded, installed fresh from new ISO) I created a new VM from Centos 7 template imported from Glance repository. It won't start, although it starts fine on my 4.2.0 host. Error upon starting VM,

[ovirt-users] Re: Update to 4.2.5, Cant start VMs

2018-08-06 Thread Vincent Royer
Upgraded from 4.2.0. None of the networks or disks show as being doubled, were your symptoms similar? I tried run once with the same result. On Mon, Aug 6, 2018, 4:09 AM Oliver Riesener wrote: > From which version do you upgrade. 4.2.4 works fine for me. > > In the past i had a similar issue

[ovirt-users] Re: Update to 4.2.5, Cant start VMs

2018-08-06 Thread Oliver Riesener
From which version do you upgrade. 4.2.4 works fine for me. In the past i had a similar issue while upgrade from x.x.x to 4.2.3 with double network and disks. I run RUN->ONCE OK (Error message ignore) OK, then run normal with RUN that fixes the issue. > Am 06.08.2018 um 06:02 schrieb Vincent Roy