[ovirt-users] Bad volume specification

2020-09-15 Thread Facundo Garat
Hi all, I'm having some issues with one VM. The VM won't start and it's showing problems with the virtual disks so I started the VM without any disks and trying to hot adding the disk and that's fail too. The servers are connected thru FC, all the other VMs are working fine. Any ideas?.

[ovirt-users] Bad Volume Specification

2019-03-27 Thread Bryan Sockel
Having an issue with starting one of my VM's. Looks like there was a problem with an auto generated snapshot on the VM. The snapshot file is missing: VDSM-Tool Output: image:52f31c3a-25ac-4930-8e67-105945dd42b5 - 461e1747-3a59-4abc-ac6a-2013ec7858d3 status:

[ovirt-users] Bad volume specification

2018-05-27 Thread Bryan Sockel
Hi, I am having to rebuild my ovirt instance for a couple of reasons. I have setup a temporary ovirt portal to migrate my setup to while i rebuild my production portal. I have run int a couple of VM's that will no longer start. Everything that i am seeing is identical to this article -

Re: [ovirt-users] Bad volume specification

2018-03-23 Thread Michal Skrivanek
> On 23 Mar 2018, at 21:02, nico...@devels.es wrote: > > El 2018-03-23 15:38, Yaniv Kaul escribió: >> On Fri, Mar 23, 2018 at 3:20 PM, wrote: >>> El 2018-03-23 12:16, Sandro Bonazzola escribió: >>> 2018-03-21 13:37 GMT+01:00 : >>> Hi, >>> We're running

Re: [ovirt-users] Bad volume specification

2018-03-23 Thread nicolas
El 2018-03-23 15:38, Yaniv Kaul escribió: On Fri, Mar 23, 2018 at 3:20 PM, wrote: El 2018-03-23 12:16, Sandro Bonazzola escribió: 2018-03-21 13:37 GMT+01:00 : Hi, We're running oVirt 4.1.9, today I put a host on maintenance, I saw one of the VMs was

Re: [ovirt-users] Bad volume specification

2018-03-23 Thread Yaniv Kaul
On Fri, Mar 23, 2018 at 3:20 PM, wrote: > El 2018-03-23 12:16, Sandro Bonazzola escribió: > >> 2018-03-21 13:37 GMT+01:00 : >> >> Hi, >>> >>> We're running oVirt 4.1.9, today I put a host on maintenance, I saw >>> one of the VMs was taking too long to

Re: [ovirt-users] Bad volume specification

2018-03-23 Thread Sandro Bonazzola
2018-03-23 13:20 GMT+01:00 : > El 2018-03-23 12:16, Sandro Bonazzola escribió: > >> 2018-03-21 13:37 GMT+01:00 : >> >> Hi, >>> >>> We're running oVirt 4.1.9, today I put a host on maintenance, I saw >>> one of the VMs was taking too long to migrate so I shut

Re: [ovirt-users] Bad volume specification

2018-03-23 Thread nicolas
El 2018-03-23 12:16, Sandro Bonazzola escribió: 2018-03-21 13:37 GMT+01:00 : Hi, We're running oVirt 4.1.9, today I put a host on maintenance, I saw one of the VMs was taking too long to migrate so I shut it down. It seems that just in that moment the machine ended

Re: [ovirt-users] Bad volume specification

2018-03-23 Thread Sandro Bonazzola
2018-03-21 13:37 GMT+01:00 : > Hi, > > We're running oVirt 4.1.9, today I put a host on maintenance, I saw one of > the VMs was taking too long to migrate so I shut it down. It seems that > just in that moment the machine ended migrating, but the shutdown did > happen as well.

Re: [ovirt-users] Bad volume specification

2018-03-23 Thread nicolas
Guys, any hints to this? El 2018-03-21 12:37, nico...@devels.es escribió: Hi, We're running oVirt 4.1.9, today I put a host on maintenance, I saw one of the VMs was taking too long to migrate so I shut it down. It seems that just in that moment the machine ended migrating, but the shutdown did

[ovirt-users] Bad volume specification

2018-03-21 Thread nicolas
Hi, We're running oVirt 4.1.9, today I put a host on maintenance, I saw one of the VMs was taking too long to migrate so I shut it down. It seems that just in that moment the machine ended migrating, but the shutdown did happen as well. Now, when I try to start the VM I'm getting the

Re: [ovirt-users] Bad volume specification after hung migration

2017-10-26 Thread Michal Skrivanek
> On 26 Oct 2017, at 12:32, Roberto Nunin wrote: > > Hi Michael > > By frozen I mean the action to put host in maintenance while some VM were > running on it. > This action wasn't completed after more than one hour. ok, and was the problem in this last VM not finishing

Re: [ovirt-users] Bad volume specification after hung migration

2017-10-26 Thread Michal Skrivanek
> On 26 Oct 2017, at 10:20, Roberto Nunin wrote: > > We are running 4.0.1.1-1.el7.centos Hi, any reason not to upgrade to 4.1? > > After a frozen migration attempt, we have two VM that after shutdown, are not > anymore able to be started up again. what do you mean by

[ovirt-users] Bad volume specification after hung migration

2017-10-26 Thread Roberto Nunin
We are running 4.0.1.1-1.el7.centos After a frozen migration attempt, we have two VM that after shutdown, are not anymore able to be started up again. Message returned is : Bad volume specification {'index': '0', u'domainID': u'731d95a9-61a7-4c7a-813b-fb1c3dde47ea', 'reqsize': '0', u'format':

Re: [ovirt-users] Bad volume specification

2017-01-05 Thread Sahina Bose
Can you provide the gluster mount logs On Fri, 6 Jan 2017 at 12:01 PM, Rodrick Brown wrote: > I'm using gluster/zfs for the backing store on my Ovirt VM's its seems our > gluster volume may have ran low on space and a few VM's we're paused due to > long i/o wait times.

[ovirt-users] Bad volume specification

2017-01-05 Thread Rodrick Brown
I'm using gluster/zfs for the backing store on my Ovirt VM's its seems our gluster volume may have ran low on space and a few VM's we're paused due to long i/o wait times. I'm no longer able to bring these VM's back online because I get the following error: OSError: [Errno 22] Invalid argument