<div dir="ltr"><div><div><div><div><div>Hi and thanks for your replies,<br><br></div>I cleaned up everything and started from scratch.<br></div><div>I using nested-kvm for my test with host-passthrough to expose vmx to the VM hypervisor, my physical CPU is a Core i5 6500<br><br></div>This time I had another problem, the VM engine won&#39;t start because of this error in vdsm.log<br>2018-03-27 22:48:31,893+0100 ERROR (vm/c9c0640e) [virt.vm] (vmId=&#39;c9c0640e-d8f1-4ade-95f3-40f2982b1d8c&#39;) The vm start process failed (vm:927)<br>Traceback (most recent call last):<br>  File &quot;/usr/lib/python2.7/site-packages/vdsm/virt/vm.py&quot;, line 856, in _startUnderlyingVm<br>    self._run()<br>  File &quot;/usr/lib/python2.7/site-packages/vdsm/virt/vm.py&quot;, line 2756, in _run<br>    dom.createWithFlags(flags)<br>  File &quot;/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py&quot;, line 130, in wrapper<br>    ret = f(*args, **kwargs)<br>  File &quot;/usr/lib/python2.7/site-packages/vdsm/common/function.py&quot;, line 92, in wrapper<br>    return func(inst, *args, **kwargs)<br>  File &quot;/usr/lib64/python2.7/site-packages/libvirt.py&quot;, line 1069, in createWithFlags<br>    if ret == -1: raise libvirtError (&#39;virDomainCreateWithFlags() failed&#39;, dom=self)<br>libvirtError:<b> internal error: Unknown CPU model SkylakeClient</b><br><br></div>The CPU model <b>SkylakeClient</b> presented to the VM engine is not recognized.<br></div>is there a way to bypass this?<br><br></div>Regards.<br></div><div class="gmail_extra"><br><div class="gmail_quote">2018-03-24 16:25 GMT+01:00 Andrei Verovski <span dir="ltr">&lt;<a href="mailto:andreil1@starlett.lv" target="_blank">andreil1@starlett.lv</a>&gt;</span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000"><span class="">
    <div class="m_-4478648151945343032moz-cite-prefix">On 03/24/2018 01:40 PM, Andy Michielsen
      wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div>Hello,</div>
      <div><br>
      </div>
      <div>I also have done a installation on my host running KVM and I
        ‘m pretty sure my vm’s can only use the <a href="http://192.168.122.0/24" target="_blank">192.168.122.0/24</a> range
        if you install them with NAT networking when creating them. So
        that might explain why you see that address appear in your log
        and also explain why the engine system can’t be reached.</div>
    </blockquote>
    <br></span>
    Can&#39;t tell fo sure about other installations, yet IMHO problem is
    with networking schema.<br>
    <br>
    One need to set bridge to real ethernet interface and add it to KVM
    VM definition.<br>
    <br>
    For example, my SuSE box have 2 ethernet cards, 192.168.0.aa for SMB
    fle server and another bridged with IP <a href="http://192.168.0.bb" target="_blank">192.168.0.bb</a> defined within
    KVM guest (CentOS 7.4 with oVirt host engine). See configs below.<br>
    <br>
    Another SuSE box have 10 Ethernet interfaces, one for for its own
    needs, and 4 + 3 for VyOS routers running as KVM guests.<br>
    <br>
    ******************************<br>
    <br>
    SU47:/etc/sysconfig/network # tail -n 100 ifcfg-br0 <br>
    BOOTPROTO=&#39;static&#39;<br>
    BRIDGE=&#39;yes&#39;<br>
    BRIDGE_FORWARDDELAY=&#39;0&#39;<br>
    BRIDGE_PORTS=&#39;eth0&#39;<br>
    BRIDGE_STP=&#39;off&#39;<br>
    BROADCAST=&#39;&#39;<br>
    DHCLIENT_SET_DEFAULT_ROUTE=&#39;<wbr>no&#39;<br>
    ETHTOOL_OPTIONS=&#39;&#39;<br>
    IPADDR=&#39;&#39;<br>
    MTU=&#39;&#39;<br>
    NETWORK=&#39;&#39;<br>
    PREFIXLEN=&#39;24&#39;<br>
    REMOTE_IPADDR=&#39;&#39;<br>
    STARTMODE=&#39;auto&#39;<br>
    NAME=&#39;&#39;<br>
    <br>
    SU47:/etc/sysconfig/network # tail -n 100 ifcfg-eth0 <br>
    BOOTPROTO=&#39;none&#39;<br>
    BROADCAST=&#39;&#39;<br>
    DHCLIENT_SET_DEFAULT_ROUTE=&#39;<wbr>no&#39;<br>
    ETHTOOL_OPTIONS=&#39;&#39;<br>
    IPADDR=&#39;&#39;<br>
    MTU=&#39;&#39;<br>
    NAME=&#39;82579LM Gigabit Network Connection&#39;<br>
    NETMASK=&#39;&#39;<br>
    NETWORK=&#39;&#39;<br>
    REMOTE_IPADDR=&#39;&#39;<br>
    STARTMODE=&#39;auto&#39;<br>
    PREFIXLEN=&#39;&#39;<div><div class="h5"><br>
    <br>
    <br>
    <blockquote type="cite">
      <div><br>
      </div>
      <div>Kind regards.</div>
      <div><br>
        On 24 Mar 2018, at 12:13, wodel youchi &lt;<a href="mailto:wodel.youchi@gmail.com" target="_blank">wodel.youchi@gmail.com</a>&gt;
        wrote:<br>
        <br>
      </div>
      <blockquote type="cite">
        <div>
          <div dir="ltr">Hi,
            <div><br>
            </div>
            <div>I am testing oVirt 4.2, I am using nested KVM for that.</div>
            <div>I am using two hypervisors Centos 7 updated and the
              hosted-Engine deployment using the ovirt appliance.</div>
            <div>For storage I am using iscsi and NFS4</div>
            <div><br>
            </div>
            <div>Versions I am using :</div>
            <div><span style="font-family:monospace"><span style="font-weight:bold;color:rgb(255,84,84)">ovirt</span><span style="color:rgb(0,0,0)">-engine-appliance-4.2-<wbr>20180214.1.el7.centos.noarch</span><br>
              </span></div>
            <div><span style="font-family:monospace"><span style="font-weight:bold;color:rgb(255,84,84)">ovirt</span><span style="color:rgb(0,0,0)">-hosted-engine-setup-2.2.<wbr>9-1.el7.centos.noarch</span><br>
              </span></div>
            <div><span style="font-family:monospace"><span style="font-weight:bold;color:rgb(255,84,84)">kernel</span><span style="color:rgb(0,0,0)">-3.10.0-693.21.1.el7.<wbr>x86_64</span><br>
              </span></div>
            <div><br>
            </div>
            <div>I have a problem deploying the hosted-engine VM, when
              configuring the deployment (hosted-engine --deploy), it
              asks for the engine&#39;s hostname then the engine&#39;s IP
              address, I use static IP, in my lab I used <b>192.168.1.104</b> as
              IP for the VM engine, and I choose to add the it&#39;s
              hostname entry to the hypervisors&#39;s /etc/hosts</div>
            <div><br>
            </div>
            <div>But the deployment get stuck every time in the same
              place : <span style="color:rgb(0,0,0);font-family:monospace"><b>TASK
                  [Wait for the host to become non operational]</b></span></div>
            <div><br>
            </div>
            <div>After some time, it gave up and the deployment fails.</div>
            <div><br>
            </div>
            <div>I don&#39;t know the reason for now, but I have seen this
              behavior in <b>/etc/hosts </b>of the hypervisor.</div>
            <div><br>
            </div>
            <div>In the beginning of the deployment the entry  <span style="color:rgb(0,0,0);font-family:monospace"><b>192.168.2.104
                  engine01.example.local</b> is added, then sometime
                after that it&#39;s deleted, then a new entry is added with
                this IP </span><span style="font-family:monospace"><b><span style="background-color:rgb(255,255,255)"><font color="#ff0000">192.168.122.65</font></span><font color="#000000"> engine01.wodel.wd</font></b><font color="#000000"> which has nothing to do with the
                  network I am using.</font></span></div>
            <div><span style="color:rgb(0,0,0);font-family:monospace"><br>
              </span></div>
            <div><span style="color:rgb(0,0,0);font-family:monospace">Here
                is the error I am seeing in the deployment log</span></div>
            <div><span style="color:rgb(0,0,0);font-family:monospace"><br>
              </span></div>
            <div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">2018-03-24 11:51:31,398+0100
                  INFO otopi.ovirt_hosted_engine_<wbr>setup.ansible_utils
                  ansible_utils._process_output:<wbr>100 TASK [Wait </span><br>
                for the host to become non operational]
                <br>
                2018-03-24 12:02:07,284+0100 DEBUG
                otopi.ovirt_hosted_engine_<wbr>setup.ansible_utils
                ansible_utils._process_output:<wbr>94 {u&#39;_ansible<br>
                _parsed&#39;: True, u&#39;_ansible_no_log&#39;: False, u&#39;changed&#39;:
                False, u&#39;attempts&#39;: 150, u&#39;invocation&#39;: {u&#39;module_args&#39;:
                {u&#39;pattern&#39;: <br>
                u&#39;name=hyperv01.wodel.wd&#39;, u&#39;fetch_nested&#39;: False,
                u&#39;nested_attributes&#39;: []}}, u&#39;ansible_facts&#39;:
                {u&#39;ovirt_hosts&#39;: []}}
                <br>
                2018-03-24 12:02:07,385+0100 ERROR
                otopi.ovirt_hosted_engine_<wbr>setup.ansible_utils
                ansible_utils._process_output:<wbr>98 fatal: [loc<br>
                alhost]: FAILED! =&gt; {&quot;ansible_facts&quot;: {&quot;ovirt_hosts&quot;:
                []}, &quot;attempts&quot;: 150, &quot;changed&quot;: false}
                <br>
                2018-03-24 12:02:07,587+0100 DEBUG
                otopi.ovirt_hosted_engine_<wbr>setup.ansible_utils
                ansible_utils._process_output:<wbr>94 PLAY RECAP <br>
                [engine01.wodel.wd] : ok: 15 changed: 8 unreachable: 0
                skipped: 4 failed: 0
                <br>
                2018-03-24 12:02:07,688+0100 DEBUG
                otopi.ovirt_hosted_engine_<wbr>setup.ansible_utils
                ansible_utils._process_output:<wbr>94 PLAY RECAP <br>
                [localhost] : ok: 41 changed: 14 unreachable: 0 skipped:
                3 failed: 1
                <br>
                2018-03-24 12:02:07,789+0100 DEBUG
                otopi.ovirt_hosted_engine_<wbr>setup.ansible_utils
                ansible_utils.run:180 ansible-playbook rc: 2
                <br>
                2018-03-24 12:02:07,790+0100 DEBUG
                otopi.ovirt_hosted_engine_<wbr>setup.ansible_utils
                ansible_utils.run:187 ansible-playbook stdou<br>
                t:<br>
              </span></div>
            <div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">2018-03-24 12:02:07,791+0100
                  DEBUG otopi.ovirt_hosted_engine_<wbr>setup.ansible_utils
                  ansible_utils.run:189  to retry, use: --limi</span><br>
                t
                @/usr/share/ovirt-hosted-<wbr>engine-setup/ansible/<wbr>bootstrap_local_vm.retry
                <br>
                <br>
                2018-03-24 12:02:07,791+0100 DEBUG
                otopi.ovirt_hosted_engine_<wbr>setup.ansible_utils
                ansible_utils.run:190 ansible-playbook stder<br>
                r:
                <br>
                2018-03-24 12:02:07,792+0100 DEBUG otopi.context
                context._executeMethod:143 method exception
                <br>
                Traceback (most recent call last):
                <br>
                 File
                &quot;/usr/lib/python2.7/site-<wbr>packages/otopi/context.py&quot;,
                line 133, in _executeMethod
                <br>
                   method[&#39;method&#39;]()
                <br>
                 File
&quot;/usr/share/ovirt-hosted-<wbr>engine-setup/scripts/../<wbr>plugins/gr-he-ansiblesetup/<wbr>core/misc.py&quot;,
                line 186, in _closeup
                <br>
                   r = ah.run()
                <br>
                 File
&quot;/usr/lib/python2.7/site-<wbr>packages/ovirt_hosted_engine_<wbr>setup/ansible_utils.py&quot;,
                line 194, in run
                <br>
                   raise RuntimeError(_(&#39;Failed executing
                ansible-playbook&#39;))
                <br>
                RuntimeError: Failed executing ansible-playbook
                <br>
                2018-03-24 12:02:07,795+0100 ERROR otopi.context
                context._executeMethod:152 Failed to execute stage
                &#39;Closing up&#39;: Failed exec<br>
                uting ansible-playbook<br>
                <br>
              </span></div>
            <div><span style="color:rgb(0,0,0);font-family:monospace"><br>
              </span></div>
            <div><span style="color:rgb(0,0,0);font-family:monospace">any
                idea????</span></div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Regards</div>
          </div>
        </div>
      </blockquote>
      <blockquote type="cite">
        <div><span>______________________________<wbr>_________________</span><br>
          <span>Users mailing list</span><br>
          <span><a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a></span><br>
          <span><a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a></span><br>
        </div>
      </blockquote>
      <br>
      <fieldset class="m_-4478648151945343032mimeAttachmentHeader"></fieldset>
      <br>
      <pre>______________________________<wbr>_________________
Users mailing list
<a class="m_-4478648151945343032moz-txt-link-abbreviated" href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>
<a class="m_-4478648151945343032moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </div></div></div>

<br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>