On Tue, Feb 14, 2017 at 2:36 PM, cmc <iucounu@gmail.com> wrote:
Hi Simone,

>>
>
> It fails due to this one:
> 2017-02-13 13:07:45,812 ERROR (vm/642a0b9a) [virt.vm]
> (vmId='642a0b9a-49fc-4ccc-8976-f6685953d0e8') The vm start process failed
> (vm:616)
> Traceback (most recent call last):
>   File "/usr/share/vdsm/virt/vm.py", line 552, in _startUnderlyingVm
>     self._run()
>   File "/usr/share/vdsm/virt/vm.py", line 1994, in _run
>     self._connection.createXML(domxml, flags),
>   File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line
> 123, in wrapper
>     ret = f(*args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 941, in
> wrapper
>     return func(inst, *args, **kwargs)
>   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3782, in
> createXML
>     if ret is None:raise libvirtError('virDomainCreateXML() failed',
> conn=self)
> libvirtError: invalid argument: could not find capabilities for arch=x86_64
> domaintype=kvm
> 2017-02-13 13:07:45,852 INFO  (vm/642a0b9a) [virt.vm]
> (vmId='642a0b9a-49fc-4ccc-8976-f6685953d0e8') Changed state to Down: invalid
> argument: could not find capabilities for arch=x86_64 domaintype=kvm
> (code=1) (vm:1199)
>
> Is your CPU properly configured for virtualization? Are you running on a
> nested env?
>

Yes, I assume it should be configured for virtualisation, since this
VM I'm creating to replace the bare-metal engine is running on one of
the two hosts that make up the cluster, and host 30 other running VMs
currently. Should it not run on the same cluster perhaps?

My steps are:

1. Create a VM on the cluster. Install the ovirt release rpm, install
the packages ovirt-hosted-engine-setup and ovirt-engine-appliance
2. run hosted-engine --deploy

...and that is as far as I have gotten so far.

OK, a bit of confusion here:
ovirt-hosted-engine-setup is going to create a VM for you based on ovirt-engine-appliance (with the engine).
If you manually create a VM (L1) on your physical host (L0) to run hosted-engine-setup there, hosted-engine-setup will create a VM (L2) for the engine running inside the L1 VM and this requires nested virtualization support which I think it's not enabled by default on oVirt hosts.
But the point is that you simply have to run ovirt-hosted-engine-setup on your physical host and not on a VM otherwise all the HA mechanism of hosted-engine will make no sense if nothing is bringing up your virtual hosts for you.

hosted-engine-setup requires an host with no others running VMs so, if it's already managed my an engine, move it to maintenance and remove it from your cluster.
 
 

Thanks,

Cam

>
>>
>> Thanks,
>>
>> Cam
>>
>>
>> On Mon, Feb 13, 2017 at 6:22 PM, Yaniv Kaul <ykaul@redhat.com> wrote:
>> >
>> > On Mon, Feb 13, 2017 at 6:26 PM, cmc <iucounu@gmail.com> wrote:
>> >>
>> >>
>> >>
>> >> /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170213141937-0wgc31.log
>> >
>> >
>> > Anything in the above log?
>> > Y.
>> >
>>
>> _______________________________________________
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>