date:20170304

Re: [ovirt-users] failed to migrate Vm

2017-03-04 Thread Arik Hadas

On Sat, Mar 4, 2017 at 8:42 PM, Bill James  wrote:

> I have a hardware node that for whatever reason most of the VM status was
> "?", even though VM was up and running fine.
>

This indicates that the engine failed to monitor the host (thus switching
VMs it knew that were running on it to the 'unknown' state).


> node was running ovirt 3.6 so I decided to upgrade it to 4.1.0.4-1 like
> most of the rest of the cluster is, including engine.
> After upgrade some VMs I'm able to start up fine on the upgraded hosts,
> other fail to start on that host and migrate themselves to another host.
> If I try to manually migrate them to the recently upgraded host migration
> fails. I have yet to find in the logs where it says why they fail.
> I am able to "runonce" the VM and tell it to start on this host and it
> starts fine.
> Why is migration failing?
>

> ovirt-engine-4.1.0.4-1.el7.centos.noarch
> vdsm-4.19.4-1.el7.centos.x86_64
>
>
> 2017-03-04 10:16:51,716-08 ERROR [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] 
> (org.ovirt.thread.pool-7-thread-48)
> [519095c3-83ed-4478-8dd4-f432db6db140] EVENT_ID:
> VM_MIGRATION_TO_SERVER_FAILED(120), Correlation ID: 2
> 6d1ecba-8711-408d-b9d5-6461a4aab4e5, Job ID: 
> 546e0e11-9b4b-48d4-bd50-2f525d049ae2,
> Call Stack: null, Custom Event ID: -1, Message: Migration failed  (VM: 
> *j2es2.test.j2noc.com
> *, Source: ovirt6.test.j2noc.com,
> Destination: *ovirt4.test.j2noc.com *)
>
>
> (engine.log attached)
>

The engine log doesn't contain the reason.
Please file a bug (https://bugzilla.redhat.com) and attach VDSM logs from
the mentioned source and destination hosts that cover the time of the
migration attempt.


>
> 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] oVirt Hosted Engine Setup fails

2017-03-04 Thread Artyom Lukianov

Please provide the ovirt-hosted-engine-setup log.

Best Regards

On Sat, Mar 4, 2017 at 4:24 PM, Manuel Luis Aznar <
manuel.luis.az...@gmail.com> wrote:

> Hello there again,
>
> The error on the first email was using the repo ovirt-release41.rpm (
> http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm), so as I
> were getting the same error again and again I am currently trying with
> ovirt-release41-snapshot.rpm (http://resources.ovirt.org/
> pub/yum-repo/ovirt-release41-snapshot.rpm) and the result is nearly the
> same.
>
> After creating the VM on the installation I got the same error with the
> command "systemctl status vdsmd":
>
> mar 04 14:10:19 host1.bajada.es vdsm[20443]: vdsm root ERROR failed to
> retrieve Hosted Engine HA info
>
> Traceback (most recent call last):
>File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line
> 231, in _getHaInfo
>   stats = instance.get_all_stats()
>File 
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
> line 102, in get_all_stats
>   with broker.connection(self._retries, self._wait):
>File "/usr/lib64/python2.7/contextlib.py", line 17, in
> __enter__
>   return self.gen.next()
>File 
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
> line 99, in connection
>   self.connect(retries, wait)
>File 
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
> line 78, in connect
>   raise BrokerConnectionError(error_msg)
>  BrokerConnectionError: Failed to connect to broker, the number of
> errors has exceeded the limit (1)
>
> mar 04 14:10:34 host1.bajada.es vdsm[20443]: vdsm
> ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR Failed to connect
> to broker, the number of errors has exceeded the limit (1)
>
> I have noticed that the ovirt-ha-agent and ovirt-ha-broker services was
> not running. I guess if this have something to do with the error in vsmd
> service log.
>
> But in this case the ovirt-hosted-engine-installation prints the vnc
> connection and I can connect to the engine VM.
>
> Thanks for all in advance
> Any help would be appreciated
> Manuel Luis Aznar
>
> 2017-03-03 21:48 GMT+00:00 Manuel Luis Aznar 
> :
>
>> Hello there,
>>
>> I am having some trouble when deploying an oVirt 4.1 hosted engine
>> installation.
>>
>> When I m just to end the installation and the hosted engine setup script
>> is about to start the Vm engine (appliance) it fails saying "The VM is not
>> powring up".
>>
>> If I double check the service vdsmd i get this error all the time:
>>
>> vdsm root ERROR failed to retrieve Hosted Engine HA info
>>  Traceback (most recent call last):
>>  File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 231,
>> in _getHaInfo
>>  stats = instance.get_all_stats()
>>  File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
>> line 102, in get_all_stats
>>  with broker.connection(self._retries, self._wait):
>>  File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
>>  return self.gen.next()
>>  File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>> line 99, in connection
>>  self.connect(retries, wait)
>>  File 
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
>> line 78, in connect
>>  raise BrokerConnectionError(error_msg)
>> BrokerConnectionError: Failed to connect to broker, the number of errors
>> has exceeded the limit (1)
>>
>> Did anyone have experimented the same problem?¿? Any hint on How to
>> solved it?¿? I have tried several times with clean installations and always
>> getting the same...
>>
>> The host where I am trying to do the installation have CentOS 7...
>>
>>
>> Thanks for all in advance
>> Will be waiting for any hint to see what I am doing wrong...
>> Manuel Luis Aznar
>>
>
>
> ___
> 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] lvscan on rhv host

2017-03-04 Thread Nir Soffer

On Sun, Mar 5, 2017 at 1:03 AM, Marcin Kruk  wrote:
> Could somebody give me a links to doc or explain behavior of lv volumes in
> RHV 4 cluster, once they are active another time they are incative, and how
> to corelate the lv volumes names with disks of virtual machines, or other
> disks?

On engine side:

- Storage domain has disks
- Disk may have one or more snapshots

On vdsm side:

- Storage domains are lvm volume groups
- Snapshot are logical volumes in the storage domain volume group
  called "volume" in vdsm.
- Disk uuid is stored as logical volume tag in each snapshot
  called "image" in vdsm.

This is correct for block storage (iSCSI, FC). File storage is
completely different
but I guess that you are interested in block storage.

On vdsm side, logical volumes must be inactive unless a logical volume is used
for running vm or for storage operation.

There are special logical volumes (inbox, outbox, master, metadata, ids, leases,
xleases) that are active when a storage domain is active.

To correlate engine and vdsm sides:

1. Find the storage domain uuid using the REST api

https://server-address/ovirt-engine/api/storagedomains/

2. List lvs in vdsm side

lvs -o name,tags vg_name

You can see the disk uuid in the IU_ tags. (Image UUID)

To locate snapshots of particular disk you can use --select

lvs --select 'lv_tags = { IU_ }' vg_name

Example:

# lvs --select 'lv_tags = {
IU_db343be2-f709-4835-b1c5-a1bbdb650b2a }'
aed577ea-d1ca-4ebe-af80-f852c7ce59bb
LV   VG
   Attr   LSize Pool Origin Data%  Meta%  Move Log Cpy%Sync
Convert
91799827-85b8-450d-a521-42de12fa08e6
aed577ea-d1ca-4ebe-af80-f852c7ce59bb -wi-ao 1.00g

Finally, you can also use vdsm-tool to show all disks on a storage domain:

# vdsm-tool dump-volume-chains aed577ea-d1ca-4ebe-af80-f852c7ce59bb

Images volume chains (base volume first)

image:239d9e96-ad7d-4a7d-83af-d593877db11b

 - 93331705-46be-4cb8-9dc2-c1559843fd4a
   status: OK, voltype: SHARED, format: COW, legality:
LEGAL, type: SPARSE


image:aab45dbc-c016-4990-b834-ce455bbc4fef

 - ea556b30-e62b-4d66-b832-459a5dd01890
   status: OK, voltype: LEAF, format: RAW, legality:
LEGAL, type: PREALLOCATED


image:db343be2-f709-4835-b1c5-a1bbdb650b2a

 - 93331705-46be-4cb8-9dc2-c1559843fd4a
   status: OK, voltype: SHARED, format: COW, legality:
LEGAL, type: SPARSE

 - 91799827-85b8-450d-a521-42de12fa08e6
   status: OK, voltype: LEAF, format: COW, legality:
LEGAL, type: SPARSE


image:7324cafc-905f-475e-8217-1a919bcca9e9

 - dfbf69fc-3371-42d4-8298-415a6ad4244a
   status: OK, voltype: LEAF, format: RAW, legality:
LEGAL, type: PREALLOCATED

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

[ovirt-users] lvscan on rhv host

2017-03-04 Thread Marcin Kruk

Could somebody give me a links to doc or explain behavior of lv volumes in
RHV 4 cluster, once they are active another time they are incative, and how
to corelate the lv volumes names with disks of virtual machines, or other
disks?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Hosted Engine Setup fails

2017-03-04 Thread Manuel Luis Aznar

Hello there again,

The error on the first email was using the repo ovirt-release41.rpm (
http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm), so as I were
getting the same error again and again I am currently trying with
ovirt-release41-snapshot.rpm (
http://resources.ovirt.org/pub/yum-repo/ovirt-release41-snapshot.rpm) and
the result is nearly the same.

After creating the VM on the installation I got the same error with the
command "systemctl status vdsmd":

mar 04 14:10:19 host1.bajada.es vdsm[20443]: vdsm root ERROR failed to
retrieve Hosted Engine HA info

Traceback (most recent call last):
   File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line
231, in _getHaInfo
  stats = instance.get_all_stats()
   File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
line 102, in get_all_stats
  with broker.connection(self._retries, self._wait):
   File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
  return self.gen.next()
   File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
line 99, in connection
  self.connect(retries, wait)
   File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
line 78, in connect
  raise BrokerConnectionError(error_msg)
 BrokerConnectionError: Failed to connect to broker, the number of
errors has exceeded the limit (1)

mar 04 14:10:34 host1.bajada.es vdsm[20443]: vdsm
ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink ERROR Failed to connect to
broker, the number of errors has exceeded the limit (1)

I have noticed that the ovirt-ha-agent and ovirt-ha-broker services was not
running. I guess if this have something to do with the error in vsmd
service log.

But in this case the ovirt-hosted-engine-installation prints the vnc
connection and I can connect to the engine VM.

Thanks for all in advance
Any help would be appreciated
Manuel Luis Aznar

2017-03-03 21:48 GMT+00:00 Manuel Luis Aznar :

> Hello there,
>
> I am having some trouble when deploying an oVirt 4.1 hosted engine
> installation.
>
> When I m just to end the installation and the hosted engine setup script
> is about to start the Vm engine (appliance) it fails saying "The VM is not
> powring up".
>
> If I double check the service vdsmd i get this error all the time:
>
> vdsm root ERROR failed to retrieve Hosted Engine HA info
>  Traceback (most recent call last):
>  File "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 231,
> in _getHaInfo
>  stats = instance.get_all_stats()
>  File 
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py",
> line 102, in get_all_stats
>  with broker.connection(self._retries, self._wait):
>  File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
>  return self.gen.next()
>  File 
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
> line 99, in connection
>  self.connect(retries, wait)
>  File 
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
> line 78, in connect
>  raise BrokerConnectionError(error_msg)
> BrokerConnectionError: Failed to connect to broker, the number of errors
> has exceeded the limit (1)
>
> Did anyone have experimented the same problem?¿? Any hint on How to solved
> it?¿? I have tried several times with clean installations and always
> getting the same...
>
> The host where I am trying to do the installation have CentOS 7...
>
>
> Thanks for all in advance
> Will be waiting for any hint to see what I am doing wrong...
> Manuel Luis Aznar
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt Nested Virtualization

2017-03-04 Thread Luca 'remix_tj' Lorenzetto

Hello,

we're installing a small ovirt cluster for hosting some test
environments at work. We're interested in testing VM running
hypervisors (i.e ovirt itself or a small openstack deployment).

Is there any documentation showing how to enable nested virtualization in ovirt?

 I've seen that while adding an host to the cluster there is the
opportunity to flag "Nested Virtualization" option, but i didn't
understand if other packages and configs are required.

Our environment is running latest ovirt 4.1 installed with ovirt-node-ng.

Luca

-- 
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)

"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)

Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Staring cluster Hosted Engine stuck - failed liveliness check

2017-03-04 Thread Maton, Brett

Doh!

  I assumed vdsm-client was part of vdsm-cli, installing vdsm-client from
the 4.1.0 release repo worked just fine.

regards,
Brett

On 4 March 2017 at 11:54, Sandro Bonazzola  wrote:

>
>
> Il 04/Mar/2017 12:21, "Maton, Brett"  ha
> scritto:
>
> I'm not sure why it's asking for vdsm-client >= 4.18.6
>
> I've got the following vdsm rpms installed:
>
> vdsm-4.19.4-1.el7.centos.x86_64
> vdsm-api-4.19.4-1.el7.centos.noarch
> vdsm-cli-4.19.4-1.el7.centos.noarch
> vdsm-hook-vmfex-dev-4.19.4-1.el7.centos.noarch
> vdsm-jsonrpc-4.19.4-1.el7.centos.noarch
> vdsm-python-4.19.4-1.el7.centos.noarch
> vdsm-xmlrpc-4.19.4-1.el7.centos.noarch
> vdsm-yajsonrpc-4.19.4-1.el7.centos.noarch
>
>
>
> Still missing vdsm-client in the list.
>
>
>
>
> On 3 March 2017 at 15:26, Maton, Brett  wrote:
>
>> Ok thanks, I'll give that another go shortly
>>
>> On 3 March 2017 at 15:24, Yaniv Kaul  wrote:
>>
>>>
>>>
>>> On Fri, Mar 3, 2017 at 5:21 PM Maton, Brett 
>>> wrote:
>>>
 Hi Simone,

   I just tried to install the RPM but got a dependency issue:

 Error: Package: ovirt-hosted-engine-ha-2.1.0.4-1.el7.centos.noarch
 (/ovirt-hosted-engine-ha-2.1.0.4-1.el7.centos.noarch)
Requires: vdsm-client >= 4.18.6

 I haven't tried to install vdsm-client as I'm not sure what impact that
 will have on the other pacakges

>>>
>>> vdsm-client is our 'next-gen' vdsClient - the CLI client to VDSM. You
>>> can and should install it in 4.1.
>>> Y.
>>>
>>>

 On 3 March 2017 at 10:59, Maton, Brett 
 wrote:

 Thanks Simone,

   I'll give that a go this evening, I'm remote at the moment.

 Regards,
 Brett

 On 3 March 2017 at 10:48, Simone Tiraboschi 
 wrote:

 On Fri, Mar 3, 2017 at 11:35 AM, Maton, Brett  wrote:

 VM Up not responding - Yes that seems to be the case.

 I did actually try hosted-engine --console

 hosted-engine --console
 The engine VM is running on this host
 Connected to domain HostedEngine
 Escape character is ^]
 error: internal error: cannot find character device 

 This was the result of https://bugzilla.redhat.com
 /show_bug.cgi?id=1364132

 Could you please install this (it's from 4.1.1 RC)
 http://resources.ovirt.org/pub/ovirt-4.1-pre/rpm/el7/noarch/
 ovirt-hosted-engine-ha-2.1.0.4-1.el7.centos.noarch.rpm to get it fixed.
 You need then to run:
 systemctl restart ovirt-ha-agent
 hosted-engine --vm-shutdown
 # wait for it
 hosted-engine --vm-start

 At this point you have should have the serial console.

 On 3 March 2017 at 08:39, Simone Tiraboschi 
 wrote:

 On Thu, Mar 2, 2017 at 11:42 AM, Maton, Brett  wrote:

 What is the correct way to shut down a cluster ?

 I shutdown my 4.1 cluster following this guide
 https://github.com/rharmonson/richtech/wiki/OSVDC-Series:-oV
 irt-3.6-Cluster-Shutdown-and-Startup as the NAS hosting the nfs mounts
 needed rebooting after updates.

 ( I realise the guide is for 3.6, surely not that different ? )

 It seams fine.

 However hosted engine isn't starting now.

   failed liveliness check

 So it seams that the engine VM is up but the engine is not responding.

 I've tried connecting from the host starting the HE vm to see what's
 going on with:

 virsh console HostedEngine

I don't know what authentication it requires, tried engine admin
 details and root os...

 hosted-engine --console

 hosted-engine --add-console-password
 Enter password:
 no graphics devices configured

 unsurprisingly, remote-viewer vnc://localhost:5900
 fails with Unable to connect to the graphic server vnc://localhost:5900

 What can I do next ?

 Check the status of the engine.

 ___
 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

>>>
>>
>
> ___
> 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] Staring cluster Hosted Engine stuck - failed liveliness check

2017-03-04 Thread Sandro Bonazzola

Il 04/Mar/2017 12:21, "Maton, Brett"  ha scritto:

I'm not sure why it's asking for vdsm-client >= 4.18.6

I've got the following vdsm rpms installed:

vdsm-4.19.4-1.el7.centos.x86_64
vdsm-api-4.19.4-1.el7.centos.noarch
vdsm-cli-4.19.4-1.el7.centos.noarch
vdsm-hook-vmfex-dev-4.19.4-1.el7.centos.noarch
vdsm-jsonrpc-4.19.4-1.el7.centos.noarch
vdsm-python-4.19.4-1.el7.centos.noarch
vdsm-xmlrpc-4.19.4-1.el7.centos.noarch
vdsm-yajsonrpc-4.19.4-1.el7.centos.noarch



Still missing vdsm-client in the list.




On 3 March 2017 at 15:26, Maton, Brett  wrote:

> Ok thanks, I'll give that another go shortly
>
> On 3 March 2017 at 15:24, Yaniv Kaul  wrote:
>
>>
>>
>> On Fri, Mar 3, 2017 at 5:21 PM Maton, Brett 
>> wrote:
>>
>>> Hi Simone,
>>>
>>>   I just tried to install the RPM but got a dependency issue:
>>>
>>> Error: Package: ovirt-hosted-engine-ha-2.1.0.4-1.el7.centos.noarch
>>> (/ovirt-hosted-engine-ha-2.1.0.4-1.el7.centos.noarch)
>>>Requires: vdsm-client >= 4.18.6
>>>
>>> I haven't tried to install vdsm-client as I'm not sure what impact that
>>> will have on the other pacakges
>>>
>>
>> vdsm-client is our 'next-gen' vdsClient - the CLI client to VDSM. You can
>> and should install it in 4.1.
>> Y.
>>
>>
>>>
>>> On 3 March 2017 at 10:59, Maton, Brett  wrote:
>>>
>>> Thanks Simone,
>>>
>>>   I'll give that a go this evening, I'm remote at the moment.
>>>
>>> Regards,
>>> Brett
>>>
>>> On 3 March 2017 at 10:48, Simone Tiraboschi  wrote:
>>>
>>>
>>>
>>> On Fri, Mar 3, 2017 at 11:35 AM, Maton, Brett 
>>> wrote:
>>>
>>> VM Up not responding - Yes that seems to be the case.
>>>
>>> I did actually try hosted-engine --console
>>>
>>> hosted-engine --console
>>> The engine VM is running on this host
>>> Connected to domain HostedEngine
>>> Escape character is ^]
>>> error: internal error: cannot find character device 
>>>
>>>
>>> This was the result of https://bugzilla.redhat.com
>>> /show_bug.cgi?id=1364132
>>>
>>> Could you please install this (it's from 4.1.1 RC)
>>> http://resources.ovirt.org/pub/ovirt-4.1-pre/rpm/el7/noarch/
>>> ovirt-hosted-engine-ha-2.1.0.4-1.el7.centos.noarch.rpm to get it fixed.
>>> You need then to run:
>>> systemctl restart ovirt-ha-agent
>>> hosted-engine --vm-shutdown
>>> # wait for it
>>> hosted-engine --vm-start
>>>
>>> At this point you have should have the serial console.
>>>
>>>
>>>
>>>
>>>
>>> On 3 March 2017 at 08:39, Simone Tiraboschi  wrote:
>>>
>>>
>>>
>>> On Thu, Mar 2, 2017 at 11:42 AM, Maton, Brett 
>>> wrote:
>>>
>>> What is the correct way to shut down a cluster ?
>>>
>>> I shutdown my 4.1 cluster following this guide
>>> https://github.com/rharmonson/richtech/wiki/OSVDC-Series:-oV
>>> irt-3.6-Cluster-Shutdown-and-Startup as the NAS hosting the nfs mounts
>>> needed rebooting after updates.
>>>
>>> ( I realise the guide is for 3.6, surely not that different ? )
>>>
>>>
>>> It seams fine.
>>>
>>>
>>>
>>> However hosted engine isn't starting now.
>>>
>>>   failed liveliness check
>>>
>>>
>>> So it seams that the engine VM is up but the engine is not responding.
>>>
>>>
>>>
>>> I've tried connecting from the host starting the HE vm to see what's
>>> going on with:
>>>
>>> virsh console HostedEngine
>>>
>>>I don't know what authentication it requires, tried engine admin
>>> details and root os...
>>>
>>>
>>> hosted-engine --console
>>>
>>>
>>>
>>> hosted-engine --add-console-password
>>> Enter password:
>>> no graphics devices configured
>>>
>>> unsurprisingly, remote-viewer vnc://localhost:5900
>>> fails with Unable to connect to the graphic server vnc://localhost:5900
>>>
>>> What can I do next ?
>>>
>>>
>>> Check the status of the engine.
>>>
>>>
>>>
>>> ___
>>> 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
>>>
>>
>

___
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] Staring cluster Hosted Engine stuck - failed liveliness check

2017-03-04 Thread Maton, Brett

I'm not sure why it's asking for vdsm-client >= 4.18.6

I've got the following vdsm rpms installed:

vdsm-4.19.4-1.el7.centos.x86_64
vdsm-api-4.19.4-1.el7.centos.noarch
vdsm-cli-4.19.4-1.el7.centos.noarch
vdsm-hook-vmfex-dev-4.19.4-1.el7.centos.noarch
vdsm-jsonrpc-4.19.4-1.el7.centos.noarch
vdsm-python-4.19.4-1.el7.centos.noarch
vdsm-xmlrpc-4.19.4-1.el7.centos.noarch
vdsm-yajsonrpc-4.19.4-1.el7.centos.noarch


On 3 March 2017 at 15:26, Maton, Brett  wrote:

> Ok thanks, I'll give that another go shortly
>
> On 3 March 2017 at 15:24, Yaniv Kaul  wrote:
>
>>
>>
>> On Fri, Mar 3, 2017 at 5:21 PM Maton, Brett 
>> wrote:
>>
>>> Hi Simone,
>>>
>>>   I just tried to install the RPM but got a dependency issue:
>>>
>>> Error: Package: ovirt-hosted-engine-ha-2.1.0.4-1.el7.centos.noarch
>>> (/ovirt-hosted-engine-ha-2.1.0.4-1.el7.centos.noarch)
>>>Requires: vdsm-client >= 4.18.6
>>>
>>> I haven't tried to install vdsm-client as I'm not sure what impact that
>>> will have on the other pacakges
>>>
>>
>> vdsm-client is our 'next-gen' vdsClient - the CLI client to VDSM. You can
>> and should install it in 4.1.
>> Y.
>>
>>
>>>
>>> On 3 March 2017 at 10:59, Maton, Brett  wrote:
>>>
>>> Thanks Simone,
>>>
>>>   I'll give that a go this evening, I'm remote at the moment.
>>>
>>> Regards,
>>> Brett
>>>
>>> On 3 March 2017 at 10:48, Simone Tiraboschi  wrote:
>>>
>>>
>>>
>>> On Fri, Mar 3, 2017 at 11:35 AM, Maton, Brett 
>>> wrote:
>>>
>>> VM Up not responding - Yes that seems to be the case.
>>>
>>> I did actually try hosted-engine --console
>>>
>>> hosted-engine --console
>>> The engine VM is running on this host
>>> Connected to domain HostedEngine
>>> Escape character is ^]
>>> error: internal error: cannot find character device 
>>>
>>>
>>> This was the result of https://bugzilla.redhat.com
>>> /show_bug.cgi?id=1364132
>>>
>>> Could you please install this (it's from 4.1.1 RC)
>>> http://resources.ovirt.org/pub/ovirt-4.1-pre/rpm/el7/noarch/
>>> ovirt-hosted-engine-ha-2.1.0.4-1.el7.centos.noarch.rpm to get it fixed.
>>> You need then to run:
>>> systemctl restart ovirt-ha-agent
>>> hosted-engine --vm-shutdown
>>> # wait for it
>>> hosted-engine --vm-start
>>>
>>> At this point you have should have the serial console.
>>>
>>>
>>>
>>>
>>>
>>> On 3 March 2017 at 08:39, Simone Tiraboschi  wrote:
>>>
>>>
>>>
>>> On Thu, Mar 2, 2017 at 11:42 AM, Maton, Brett 
>>> wrote:
>>>
>>> What is the correct way to shut down a cluster ?
>>>
>>> I shutdown my 4.1 cluster following this guide
>>> https://github.com/rharmonson/richtech/wiki/OSVDC-Series:-oV
>>> irt-3.6-Cluster-Shutdown-and-Startup as the NAS hosting the nfs mounts
>>> needed rebooting after updates.
>>>
>>> ( I realise the guide is for 3.6, surely not that different ? )
>>>
>>>
>>> It seams fine.
>>>
>>>
>>>
>>> However hosted engine isn't starting now.
>>>
>>>   failed liveliness check
>>>
>>>
>>> So it seams that the engine VM is up but the engine is not responding.
>>>
>>>
>>>
>>> I've tried connecting from the host starting the HE vm to see what's
>>> going on with:
>>>
>>> virsh console HostedEngine
>>>
>>>I don't know what authentication it requires, tried engine admin
>>> details and root os...
>>>
>>>
>>> hosted-engine --console
>>>
>>>
>>>
>>> hosted-engine --add-console-password
>>> Enter password:
>>> no graphics devices configured
>>>
>>> unsurprisingly, remote-viewer vnc://localhost:5900
>>> fails with Unable to connect to the graphic server vnc://localhost:5900
>>>
>>> What can I do next ?
>>>
>>>
>>> Check the status of the engine.
>>>
>>>
>>>
>>> ___
>>> 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
>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] HE vm fails to migrate due to host CPU incompatibility even after changing cluster CPU type

2017-03-04 Thread Stefano Stagnaro


Hi guys,

I've started an oVirt 4.1 HE deployment on a Broadwell based server. 
Then I added to HE a second, older host based on Nehalem. I've 
downgraded the cluster CPU type to Nehalem to accommodate host2 and it 
finally reached score 3400. However, when I try to migrate HE vm it 
fails with the following error:


2017-03-03 20:19:51,814 ERROR (migsrc/b0d38435) [virt.vm] 
(vmId='b0d38435-5774-4ca9-ad24-70b57b5bc25d') unsupported configuration: 
guest and host CPU are not compatible: Host CPU does not provide 
required features: pclmuldq, fma, pcid, x2apic, movbe, tsc-deadline, 
aes, xsave, avx, fsgsbase, bmi1, hle, avx2, smep, bmi2, erms, invpcid, 
rtm, rdseed, adx, smap, 3dnowprefetch; try using 'Broadwell-noTSX' CPU 
model (migration:265)


I believe the problem is in the HE vm XML where the cpu is still 
configured as Broadwell. how can I change this specific setting without 
losing the deployment? Please find all the relevant logs at the 
following link: 
https://www.dropbox.com/sh/njl9aofhdw10ses/AADf2Ql4GKVIKcbgLivbmjC2a


Besides that, I believe this is a wrong behavior because HE should 
follow cluster properties (otherwise do not reach score 3400); do you 
believe is it worth opening a issue on bugzilla?


Thank you,
Stefano.

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

Re: [ovirt-users] failed to migrate Vm

Re: [ovirt-users] oVirt Hosted Engine Setup fails

Re: [ovirt-users] lvscan on rhv host

[ovirt-users] lvscan on rhv host

Re: [ovirt-users] oVirt Hosted Engine Setup fails

[ovirt-users] oVirt Nested Virtualization

Re: [ovirt-users] Staring cluster Hosted Engine stuck - failed liveliness check

Re: [ovirt-users] Staring cluster Hosted Engine stuck - failed liveliness check

Re: [ovirt-users] Staring cluster Hosted Engine stuck - failed liveliness check

[ovirt-users] HE vm fails to migrate due to host CPU incompatibility even after changing cluster CPU type

10 matches

Site Navigation

Mail list logo

Footer information