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 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.
>>> I would suggest to update to 4.2 as soon as possible since 4.1 is
>>> not
>>> supported anymore now that 4.2 is available
>> We have 2 oVirt infrastructures. One is migrated to 4.2, we can't
>> migrate the other one since most of the user portal features in 4.1
>> are not present in 4.2 and our users do a massive usage of this portal
>> to create/tune VMs. I know several issues were created on Github to
>> implement missing features, but we cannot upgrade until they are
>> implemented.
>> Have you checked the latest oVirt 4.2.2 RC? We have brought back
>> several features to the user portal.
>> Y.
>>  
> 
> Yes, I'm aware. I'm about to find some time to test it, still I think there 
> will be some features missing (I think I've read that it won't be possible to 
> deploy a VM without a template),

“Blank” is also a template:) There’s basic disk and network creation

> but I need to test it for a while. Still I guess we can upgrade and let some 
> teachers test if they can get used to the new user portal.

it’s not yet out, had some issues building dependencies today. Should be ready 
early next week

> 
> Thank you!
> 
>>> Thanks.
>>>  
>>> Now, when I try to start the VM I'm getting the following error:
>>> 2018-03-21 12:31:02,309Z ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>>> (DefaultQuartzScheduler3) [7985a4e2] EVENT_ID: VM_DOWN_ERROR(119),
>>> Correlation ID: null, Call Stack: null, Custom ID: null, Custom
>>> Event ID: -1, Message: VM openmaint.iaas.domain.com 
>>>  [1] [1] is down
>>> with
>>> error. Exit message: Bad volume specification {'index': '0',
>>> u'domainID': u'04cb5bd0-d94e-4d14-a71a-e63a669e11b9', 'reqsize':
>>> '0', u'format': u'cow', u'optional': u'false', u'address':
>>> {u'function': u'0x0', u'bus': u'0x00', u'domain': u'0x',
>>> u'type': u'pci', u'slot': u'0x06'}, u'volumeID':
>>> u'68ee7a04-ceff-49f0-bf91-256870543921', 'apparentsize':
>>> '3221225472', u'imageID': u'9d087e6b-0832-46db-acb0-16d5131afa0c',
>>> u'discard': False, u'specParams': {}, u'readonly': u'false',
>>> u'iface': u'virtio', u'deviceId':
>>> u'9d087e6b-0832-46db-acb0-16d5131afa0c', 'truesize': '3221225472',
>>> u'poolID': u'75bf8f48-970f-42bc-8596-f8ab6efb2b63', u'device':
>>> u'disk', u'shared': u'false', u'propagateErrors': u'off', u'type':
>>> u'disk'}.
>>> It looks quite bad... I'm attaching the engine.log since the moment
>>> I start the VM.
>>> Is there anything I can do to recover the VM? oVirt says the disk
>>> is OK in the 'Disks' tab.
>>> Adding some people who may be able to help. Once solved, please
>>> consider upgrade.
>>>  
>>> Thanks.
>>> ___
>>> Users mailing list
>>> Users@ovirt.org 
>>> http://lists.ovirt.org/mailman/listinfo/users 
>>>  [2] [2]
>>> --
>>> SANDRO BONAZZOLA
>>> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION
>>> R&D
>>> Red Hat EMEA [3]
>>> sbona...@redhat.com    
>>>  [4]
>>>  [5]
>>> Links:
>>> --
>>> [1] http://openmaint.iaas.domain.com  [1]
>>> [2] http://lists.ovirt.org/mailman/listinfo/users 
>>>  [2]
>>> [3] https://www.redhat.com/  [3]
>>> [4] https://red.ht/sig  [4]
>>> [5] https://redhat.com/summit  [5]
>> ___
>> Users mailing list
>> Users@ovirt.org 
>> http://lists.ovirt.org/mailman/listinfo/users 
>>  [2]
>> Links:
>> --
>> [1] http://openmaint.iaas.domain.com 
>> [2] http://lists.ovirt.org/mailman/listinfo/users 
>> 
>> [3] https://www.redhat.com/ 
>> [4] https://red.ht/sig 
>> [5] https://redhat.com/summit 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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 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.

I would suggest to update to 4.2 as soon as possible since 4.1 is
not
supported anymore now that 4.2 is available


 We have 2 oVirt infrastructures. One is migrated to 4.2, we can't
migrate the other one since most of the user portal features in 4.1
are not present in 4.2 and our users do a massive usage of this portal
to create/tune VMs. I know several issues were created on Github to
implement missing features, but we cannot upgrade until they are
implemented.

Have you checked the latest oVirt 4.2.2 RC? We have brought back
several features to the user portal.
Y.
 


Yes, I'm aware. I'm about to find some time to test it, still I think 
there will be some features missing (I think I've read that it won't be 
possible to deploy a VM without a template), but I need to test it for a 
while. Still I guess we can upgrade and let some teachers test if they 
can get used to the new user portal.


Thank you!




Thanks.

 

Now, when I try to start the VM I'm getting the following error:

2018-03-21 12:31:02,309Z ERROR



[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]

(DefaultQuartzScheduler3) [7985a4e2] EVENT_ID: VM_DOWN_ERROR(119),
Correlation ID: null, Call Stack: null, Custom ID: null, Custom
Event ID: -1, Message: VM openmaint.iaas.domain.com [1] [1] is down
with
error. Exit message: Bad volume specification {'index': '0',
u'domainID': u'04cb5bd0-d94e-4d14-a71a-e63a669e11b9', 'reqsize':
'0', u'format': u'cow', u'optional': u'false', u'address':
{u'function': u'0x0', u'bus': u'0x00', u'domain': u'0x',
u'type': u'pci', u'slot': u'0x06'}, u'volumeID':
u'68ee7a04-ceff-49f0-bf91-256870543921', 'apparentsize':
'3221225472', u'imageID': u'9d087e6b-0832-46db-acb0-16d5131afa0c',
u'discard': False, u'specParams': {}, u'readonly': u'false',
u'iface': u'virtio', u'deviceId':
u'9d087e6b-0832-46db-acb0-16d5131afa0c', 'truesize': '3221225472',
u'poolID': u'75bf8f48-970f-42bc-8596-f8ab6efb2b63', u'device':
u'disk', u'shared': u'false', u'propagateErrors': u'off', u'type':
u'disk'}.

It looks quite bad... I'm attaching the engine.log since the moment
I start the VM.

Is there anything I can do to recover the VM? oVirt says the disk
is OK in the 'Disks' tab.

Adding some people who may be able to help. Once solved, please
consider upgrade.

 

Thanks.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users [2] [2]

--

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION
R&D

Red Hat EMEA [3]

sbona...@redhat.com   

                 [4]

 [5]

Links:
--
[1] http://openmaint.iaas.domain.com [1]
[2] http://lists.ovirt.org/mailman/listinfo/users [2]
[3] https://www.redhat.com/ [3]
[4] https://red.ht/sig [4]
[5] https://redhat.com/summit [5]


 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users [2]



Links:
--
[1] http://openmaint.iaas.domain.com
[2] http://lists.ovirt.org/mailman/listinfo/users
[3] https://www.redhat.com/
[4] https://red.ht/sig
[5] https://redhat.com/summit

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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 migrate so I shut it down. It
>>> seems that just in that moment the machine ended migrating, but the
>>> shutdown did happen as well.
>>>
>>
>> I would suggest to update to 4.2 as soon as possible since 4.1 is not
>> supported anymore now that 4.2 is available
>>
>>
> We have 2 oVirt infrastructures. One is migrated to 4.2, we can't migrate
> the other one since most of the user portal features in 4.1 are not present
> in 4.2 and our users do a massive usage of this portal to create/tune VMs.
> I know several issues were created on Github to implement missing features,
> but we cannot upgrade until they are implemented.
>

Have you checked the latest oVirt 4.2.2 RC? We have brought back several
features to the user portal.
Y.


>
> Thanks.
>
>
>>
>> Now, when I try to start the VM I'm getting the following error:
>>>
>>> 2018-03-21 12:31:02,309Z ERROR
>>>
>>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>>
>>> (DefaultQuartzScheduler3) [7985a4e2] EVENT_ID: VM_DOWN_ERROR(119),
>>> Correlation ID: null, Call Stack: null, Custom ID: null, Custom
>>> Event ID: -1, Message: VM openmaint.iaas.domain.com [1] is down with
>>> error. Exit message: Bad volume specification {'index': '0',
>>> u'domainID': u'04cb5bd0-d94e-4d14-a71a-e63a669e11b9', 'reqsize':
>>> '0', u'format': u'cow', u'optional': u'false', u'address':
>>> {u'function': u'0x0', u'bus': u'0x00', u'domain': u'0x',
>>> u'type': u'pci', u'slot': u'0x06'}, u'volumeID':
>>> u'68ee7a04-ceff-49f0-bf91-256870543921', 'apparentsize':
>>> '3221225472', u'imageID': u'9d087e6b-0832-46db-acb0-16d5131afa0c',
>>> u'discard': False, u'specParams': {}, u'readonly': u'false',
>>> u'iface': u'virtio', u'deviceId':
>>> u'9d087e6b-0832-46db-acb0-16d5131afa0c', 'truesize': '3221225472',
>>> u'poolID': u'75bf8f48-970f-42bc-8596-f8ab6efb2b63', u'device':
>>> u'disk', u'shared': u'false', u'propagateErrors': u'off', u'type':
>>> u'disk'}.
>>>
>>> It looks quite bad... I'm attaching the engine.log since the moment
>>> I start the VM.
>>>
>>> Is there anything I can do to recover the VM? oVirt says the disk
>>> is OK in the 'Disks' tab.
>>>
>>
>> Adding some people who may be able to help. Once solved, please
>> consider upgrade.
>>
>>
>>
>> Thanks.
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users [2]
>>>
>>
>> --
>>
>> SANDRO BONAZZOLA
>>
>> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
>>
>> Red Hat EMEA [3]
>>
>> sbona...@redhat.com
>>
>>  [4]
>>
>>  [5]
>>
>>
>>
>> Links:
>> --
>> [1] http://openmaint.iaas.domain.com
>> [2] http://lists.ovirt.org/mailman/listinfo/users
>> [3] https://www.redhat.com/
>> [4] https://red.ht/sig
>> [5] https://redhat.com/summit
>>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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 it down. It
>>> seems that just in that moment the machine ended migrating, but the
>>> shutdown did happen as well.
>>>
>>
>> I would suggest to update to 4.2 as soon as possible since 4.1 is not
>> supported anymore now that 4.2 is available
>>
>>
> We have 2 oVirt infrastructures. One is migrated to 4.2, we can't migrate
> the other one since most of the user portal features in 4.1 are not present
> in 4.2 and our users do a massive usage of this portal to create/tune VMs.
> I know several issues were created on Github to implement missing features,
> but we cannot upgrade until they are implemented.
>

Understood, thanks for the feedback!


>
> Thanks.
>
>
>>
>> Now, when I try to start the VM I'm getting the following error:
>>>
>>> 2018-03-21 12:31:02,309Z ERROR
>>>
>>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>>
>>> (DefaultQuartzScheduler3) [7985a4e2] EVENT_ID: VM_DOWN_ERROR(119),
>>> Correlation ID: null, Call Stack: null, Custom ID: null, Custom
>>> Event ID: -1, Message: VM openmaint.iaas.domain.com [1] is down with
>>> error. Exit message: Bad volume specification {'index': '0',
>>> u'domainID': u'04cb5bd0-d94e-4d14-a71a-e63a669e11b9', 'reqsize':
>>> '0', u'format': u'cow', u'optional': u'false', u'address':
>>> {u'function': u'0x0', u'bus': u'0x00', u'domain': u'0x',
>>> u'type': u'pci', u'slot': u'0x06'}, u'volumeID':
>>> u'68ee7a04-ceff-49f0-bf91-256870543921', 'apparentsize':
>>> '3221225472', u'imageID': u'9d087e6b-0832-46db-acb0-16d5131afa0c',
>>> u'discard': False, u'specParams': {}, u'readonly': u'false',
>>> u'iface': u'virtio', u'deviceId':
>>> u'9d087e6b-0832-46db-acb0-16d5131afa0c', 'truesize': '3221225472',
>>> u'poolID': u'75bf8f48-970f-42bc-8596-f8ab6efb2b63', u'device':
>>> u'disk', u'shared': u'false', u'propagateErrors': u'off', u'type':
>>> u'disk'}.
>>>
>>> It looks quite bad... I'm attaching the engine.log since the moment
>>> I start the VM.
>>>
>>> Is there anything I can do to recover the VM? oVirt says the disk
>>> is OK in the 'Disks' tab.
>>>
>>
>> Adding some people who may be able to help. Once solved, please
>> consider upgrade.
>>
>>
>>
>> Thanks.
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users [2]
>>>
>>
>> --
>>
>> SANDRO BONAZZOLA
>>
>> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
>>
>> Red Hat EMEA [3]
>>
>> sbona...@redhat.com
>>
>>  [4]
>>
>>  [5]
>>
>>
>>
>> Links:
>> --
>> [1] http://openmaint.iaas.domain.com
>> [2] http://lists.ovirt.org/mailman/listinfo/users
>> [3] https://www.redhat.com/
>> [4] https://red.ht/sig
>> [5] https://redhat.com/summit
>>
>


-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA 

sbona...@redhat.com


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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 migrating, but the
shutdown did happen as well.


I would suggest to update to 4.2 as soon as possible since 4.1 is not
supported anymore now that 4.2 is available



We have 2 oVirt infrastructures. One is migrated to 4.2, we can't 
migrate the other one since most of the user portal features in 4.1 are 
not present in 4.2 and our users do a massive usage of this portal to 
create/tune VMs. I know several issues were created on Github to 
implement missing features, but we cannot upgrade until they are 
implemented.


Thanks.


 


Now, when I try to start the VM I'm getting the following error:

2018-03-21 12:31:02,309Z ERROR


[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]

(DefaultQuartzScheduler3) [7985a4e2] EVENT_ID: VM_DOWN_ERROR(119),
Correlation ID: null, Call Stack: null, Custom ID: null, Custom
Event ID: -1, Message: VM openmaint.iaas.domain.com [1] is down with
error. Exit message: Bad volume specification {'index': '0',
u'domainID': u'04cb5bd0-d94e-4d14-a71a-e63a669e11b9', 'reqsize':
'0', u'format': u'cow', u'optional': u'false', u'address':
{u'function': u'0x0', u'bus': u'0x00', u'domain': u'0x',
u'type': u'pci', u'slot': u'0x06'}, u'volumeID':
u'68ee7a04-ceff-49f0-bf91-256870543921', 'apparentsize':
'3221225472', u'imageID': u'9d087e6b-0832-46db-acb0-16d5131afa0c',
u'discard': False, u'specParams': {}, u'readonly': u'false',
u'iface': u'virtio', u'deviceId':
u'9d087e6b-0832-46db-acb0-16d5131afa0c', 'truesize': '3221225472',
u'poolID': u'75bf8f48-970f-42bc-8596-f8ab6efb2b63', u'device':
u'disk', u'shared': u'false', u'propagateErrors': u'off', u'type':
u'disk'}.

It looks quite bad... I'm attaching the engine.log since the moment
I start the VM.

Is there anything I can do to recover the VM? oVirt says the disk
is OK in the 'Disks' tab.


Adding some people who may be able to help. Once solved, please
consider upgrade.

 


Thanks.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users [2]


--

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA [3]

sbona...@redhat.com   

 [4]

 [5]



Links:
--
[1] http://openmaint.iaas.domain.com
[2] http://lists.ovirt.org/mailman/listinfo/users
[3] https://www.redhat.com/
[4] https://red.ht/sig
[5] https://redhat.com/summit

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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.
>

I would suggest to update to 4.2 as soon as possible since 4.1 is not
supported anymore now that 4.2 is available



>
> Now, when I try to start the VM I'm getting the following error:
>
> 2018-03-21 12:31:02,309Z ERROR [org.ovirt.engine.core.dal.dbb
> roker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler3)
> [7985a4e2] EVENT_ID: VM_DOWN_ERROR(119), Correlation ID: null, Call Stack:
> null, Custom ID: null, Custom Event ID: -1, Message: VM
> openmaint.iaas.domain.com is down with error. Exit message: Bad volume
> specification {'index': '0', u'domainID': 
> u'04cb5bd0-d94e-4d14-a71a-e63a669e11b9',
> 'reqsize': '0', u'format': u'cow', u'optional': u'false', u'address':
> {u'function': u'0x0', u'bus': u'0x00', u'domain': u'0x', u'type':
> u'pci', u'slot': u'0x06'}, u'volumeID': 
> u'68ee7a04-ceff-49f0-bf91-256870543921',
> 'apparentsize': '3221225472', u'imageID': 
> u'9d087e6b-0832-46db-acb0-16d5131afa0c',
> u'discard': False, u'specParams': {}, u'readonly': u'false', u'iface':
> u'virtio', u'deviceId': u'9d087e6b-0832-46db-acb0-16d5131afa0c',
> 'truesize': '3221225472', u'poolID': u'75bf8f48-970f-42bc-8596-f8ab6efb2b63',
> u'device': u'disk', u'shared': u'false', u'propagateErrors': u'off',
> u'type': u'disk'}.
>
> It looks quite bad... I'm attaching the engine.log since the moment I
> start the VM.
>
> Is there anything I can do to recover the VM? oVirt says the disk is OK in
> the 'Disks' tab.
>

Adding some people who may be able to help. Once solved, please consider
upgrade.




>
> Thanks.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA 

sbona...@redhat.com


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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 happen as well.

Now, when I try to start the VM I'm getting the following error:

2018-03-21 12:31:02,309Z ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler3) [7985a4e2] EVENT_ID: VM_DOWN_ERROR(119),
Correlation ID: null, Call Stack: null, Custom ID: null, Custom Event
ID: -1, Message: VM openmaint.iaas.domain.com is down with error. Exit
message: Bad volume specification {'index': '0', u'domainID':
u'04cb5bd0-d94e-4d14-a71a-e63a669e11b9', 'reqsize': '0', u'format':
u'cow', u'optional': u'false', u'address': {u'function': u'0x0',
u'bus': u'0x00', u'domain': u'0x', u'type': u'pci', u'slot':
u'0x06'}, u'volumeID': u'68ee7a04-ceff-49f0-bf91-256870543921',
'apparentsize': '3221225472', u'imageID':
u'9d087e6b-0832-46db-acb0-16d5131afa0c', u'discard': False,
u'specParams': {}, u'readonly': u'false', u'iface': u'virtio',
u'deviceId': u'9d087e6b-0832-46db-acb0-16d5131afa0c', 'truesize':
'3221225472', u'poolID': u'75bf8f48-970f-42bc-8596-f8ab6efb2b63',
u'device': u'disk', u'shared': u'false', u'propagateErrors': u'off',
u'type': u'disk'}.

It looks quite bad... I'm attaching the engine.log since the moment I
start the VM.

Is there anything I can do to recover the VM? oVirt says the disk is
OK in the 'Disks' tab.

Thanks.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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 the migration? Was it 
migrating at all? If yes, what was the progress in UI, any failures? There are 
various timeouts which should have been triggered, so if they were not 
triggered it would indeed point to some internal issue. Would be great to 
attach source and destination vdsm.log

> Thinking that shutting down the VM could help, I've done it. Looking at 
> results, not.

What was the result? Did it fail to shut down? Did you use Power Off to force 
immediate shutdown? If it was migrating, did you try to cancel the migration 
first?

> 
> Yes, I've restarted the ovirt-engine service, I've still not restarted the 
> hosted-engine VM.

well, it’s not only a universal “fix” of various things, sometimes it does more 
harm than benefit too. Logs would be helpful.

> Hosts still not restarted. Do you think can help ?

hard to say. Either way please salvage logs first

> 
> Obviously we will migrate, this activities are enabling us to have redundancy 
> at the storage level, then we will migrate to 4.1.x

great:)

Thanks,
michal

> 
> Thanks
> 
> 2017-10-26 12:26 GMT+02:00 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 frozen? Are you talking about "VM live migration" or 
> “live storage migration”?
> How exactly did you resolve that situation, you only shut down those VMs? No 
> other troubleshooting steps, e.g. restarting engine, hosts, things like that?
> 
> Thanks,
> michal
>> 
>> Message returned is :
>> 
>> Bad volume specification {'index': '0', u'domainID': 
>> u'731d95a9-61a7-4c7a-813b-fb1c3dde47ea', 'reqsize': '0', u'format': u'cow', 
>> u'optional': u'false', u'address': {u'function': u'0x0', u'bus': u'0x00', 
>> u'domain': u'0x', u'type': u'pci', u'slot': u'0x05'}, u'volumeID': 
>> u'cffc70ff-ed72-46ef-a369-4be95de72260', 'apparentsize': '3221225472', 
>> u'imageID': u'3fe5a849-bcc2-42d3-93c5aca4c504515b', u'specParams': {}, 
>> u'readonly': u'false', u'iface': u'virtio', u'deviceId': 
>> u'3fe5a849bcc2-42d3-93c5-aca4c504515b', 'truesize': '3221225472', u'poolID': 
>> u'0001-0001-0001-0001-01ec', u'device': u'disk', u'shared': 
>> u'false', u'propagateErrors': u'off',u'type':u'disk'}
>> 
>> Probably this is caused by a wrong pointer into the database that still 
>> refer to the migration image-id.
>> 
>> If we search within all_disks view, we can find that parentid field isn't 
>> ---- like all other running vm, but it has a 
>> value:
>> 
>>vm_names   |   parentid
>> --+--
>>  working01.company.xx | ----
>>  working02.company.xx | ----
>>  working03.company.xx | ----
>>  working04.company.xx | ----
>>  broken001.company.xx | 30533842-2c83-4d0e-95d2-48162dbe23bd <
>>  working05.company.xx | ----
>> 
>> 
>> How we can recover from this ?
>> 
>> Thanks in advance
>> Regards,
>> 
>> -- 
>> Robert​o​
>> 
>> 
>> 
>> ___
>> Users mailing list
>> Users@ovirt.org 
>> http://lists.ovirt.org/mailman/listinfo/users 
>> 
> 
> 
> 
> 
> -- 
> Roberto
> 
> 
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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 frozen? Are you talking about "VM live migration" or “live 
storage migration”?
How exactly did you resolve that situation, you only shut down those VMs? No 
other troubleshooting steps, e.g. restarting engine, hosts, things like that?

Thanks,
michal
> 
> Message returned is :
> 
> Bad volume specification {'index': '0', u'domainID': 
> u'731d95a9-61a7-4c7a-813b-fb1c3dde47ea', 'reqsize': '0', u'format': u'cow', 
> u'optional': u'false', u'address': {u'function': u'0x0', u'bus': u'0x00', 
> u'domain': u'0x', u'type': u'pci', u'slot': u'0x05'}, u'volumeID': 
> u'cffc70ff-ed72-46ef-a369-4be95de72260', 'apparentsize': '3221225472', 
> u'imageID': u'3fe5a849-bcc2-42d3-93c5aca4c504515b', u'specParams': {}, 
> u'readonly': u'false', u'iface': u'virtio', u'deviceId': 
> u'3fe5a849bcc2-42d3-93c5-aca4c504515b', 'truesize': '3221225472', u'poolID': 
> u'0001-0001-0001-0001-01ec', u'device': u'disk', u'shared': 
> u'false', u'propagateErrors': u'off',u'type':u'disk'}
> 
> Probably this is caused by a wrong pointer into the database that still refer 
> to the migration image-id.
> 
> If we search within all_disks view, we can find that parentid field isn't 
> ---- like all other running vm, but it has a 
> value:
> 
>vm_names   |   parentid
> --+--
>  working01.company.xx | ----
>  working02.company.xx | ----
>  working03.company.xx | ----
>  working04.company.xx | ----
>  broken001.company.xx | 30533842-2c83-4d0e-95d2-48162dbe23bd <
>  working05.company.xx | ----
> 
> 
> How we can recover from this ?
> 
> Thanks in advance
> Regards,
> 
> -- 
> Robert​o​
> 
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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.
>
> I'm no longer able to bring these VM's back online because I get the
> following error:
>
> OSError: [Errno 22] Invalid argument
> Thread-991494::ERROR::2017-01-06
> 01:17:32,990::vm::759::virt.vm::(_startUnderlyingVm)
> vmId=`add4f65a-6389-4fc8-bf9d-bf92964cecf0`::The vm start process failed
> Traceback (most recent call last):
>   File "/usr/sha
>
> ​StorageUnavailableError: Unable to get volume size for domain domain 
> volume 
>
> I have snapshots is their anyway I can recover or fix this issue? ​
>
>
>
>
> ___
>
> Users mailing list
>
> Users@ovirt.org
>
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users