<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 14, 2016 at 11:56 AM, Maton, Brett <span dir="ltr"><<a href="mailto:matonb@ltresources.co.uk" target="_blank">matonb@ltresources.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>Ah ok, the VM I'm running <code>hosted-engine --deploy</code> on indeed doesn;t have the vmx flag.<br><br></div>( the previous result was from the physical host running the VM ).<br><br></div>I've had a quick look through the options, but can't see where I could enable vmx or change the settings for the VM itself.<br></div></blockquote><div><br></div><div>Sorry but I don't understand the scenario.</div><div><br></div><div>hosted-engine-setup has to be installed and executed on the host you are going to use to run a VM which will contain the engine; while are you running it on a VM?</div><div>You can do it for test purposes but it's not recommended for the production usage.</div><div>In that case you need nested virtualization support on your physical host since you are going to create a VM for your hosted-engine host and then you are going to start a nested VM there. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br></div><div class="gmail-HOEnZb"><div class="gmail-h5"><div class="gmail_extra"><br><div class="gmail_quote">On 14 September 2016 at 10:50, Simone Tiraboschi <span dir="ltr"><<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Sep 14, 2016 at 11:40 AM, Simone Tiraboschi <span dir="ltr"><<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Sep 14, 2016 at 11:39 AM, Maton, Brett <span dir="ltr"><<a href="mailto:matonb@ltresources.co.uk" target="_blank">matonb@ltresources.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>The vmx cpu flag is present, is that what you mean ?<br></div></div></blockquote><div><br></div></span><div>Yes, let me double check VDSM logs.</div><div><div><div><br></div></div></div></div></div></div></blockquote><div><br></div></span><div>The issue is indeed here:</div><div><div>Thread-89::ERROR::2016-09-13 19:45:58,188::vm::765::virt.vm<wbr>::(_startUnderlyingVm) vmId=`1ed592d3-2b69-4901-9ff6-<wbr>fe21d1dff8c5`::The vm start process failed</div><span><div>Traceback (most recent call last):</div></span><div> File "/usr/share/vdsm/virt/vm.py", line 706, in _startUnderlyingVm</div><div> self._run()</div><div> File "/usr/share/vdsm/virt/vm.py", line 1996, in _run</div><div> self._connection.createXML(dom<wbr>xml, flags),</div><div> File "/usr/lib/python2.7/site-packa<wbr>ges/vdsm/libvirtconnection.py"<wbr>, line 123, in wrapper</div><div> ret = f(*args, **kwargs)</div><div> File "/usr/lib/python2.7/site-packa<wbr>ges/vdsm/utils.py", line 916, in wrapper</div><div> return func(inst, *args, **kwargs)</div><div> File "/usr/lib64/python2.7/site-pac<wbr>kages/libvirt.py", line 3611, in createXML</div><div> if ret is None:raise libvirtError('virDomainCreateX<wbr>ML() failed', conn=self)</div><div>libvirtError: invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm </div><div>Thread-89::INFO::2016-09-13 19:45:58,192::vm::1308::virt.v<wbr>m::(setDownStatus) vmId=`1ed592d3-2b69-4901-9ff6-<wbr>fe21d1dff8c5`::Changed state to Down: invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm (code=1)</div></div><div><br></div><div>And VDSM returns just </div><div>'cpuFlags': 'fpu,vme,de,pse,tsc,msr,pae,mc<wbr>e,cx8,apic,sep,mtrr,pge,mca,cm<wbr>ov,pat,pse36,clflush,mmx,fxsr,<wbr>sse,sse2,syscall,nx,rdtscp,lm,<wbr>constant_tsc,rep_good,nopl,<wbr>eagerfpu,pni,pclmulqdq,ssse3,<wbr>fma,cx16,pcid,sse4_1,sse4_2,<wbr>x2apic,movbe,popcnt,tsc_<wbr>deadline_timer,aes,xsave,avx,<wbr>f16c,rdrand,hypervisor,lahf_<wbr>lm,fsgsbase,bmi1,avx2,smep,<wbr>bmi2,erms,invpcid,xsaveopt,<wbr>model_Haswell-noTSX,model_<wbr>Nehalem,model_Conroe,model_<wbr>Penryn,model_IvyBridge,model_W<wbr>estmere,model_SandyBridge'<br></div><div><br></div><div>without vmx!</div><div><div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div><div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br># grep flags /proc/cpuinfo | grep -c ' vmx '<br>48<br><br></div>Trying to avoid rebooting the server if possible...<br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On 14 September 2016 at 10:16, Simone Tiraboschi <span dir="ltr"><<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Sep 14, 2016 at 11:05 AM, Maton, Brett <span dir="ltr"><<a href="mailto:matonb@ltresources.co.uk" target="_blank">matonb@ltresources.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Oops :)<br><br></div>hosted setup log attached.<br></div></blockquote><div><br></div></span><div>Your issue is probably here:<br></div><div><div>2016-09-13 19:41:52 DEBUG otopi.ovirt_host_deploy.hardwa<wbr>re hardware.detect:210 Cannot detect virualization</div><div>Traceback (most recent call last):</div><div> File "/usr/lib/python2.7/site-packa<wbr>ges/ovirt_host_deploy/hardware<wbr>.py", line 199, in detect</div><div> if self._isVirtualizationEnabled(<wbr>):</div><div> File "/usr/lib/python2.7/site-packa<wbr>ges/ovirt_host_deploy/hardware<wbr>.py", line 175, in _isVirtualizationEnabled</div><div> bios_ok = self._vmx_enabled_by_bios()</div><div> File "/usr/lib/python2.7/site-packa<wbr>ges/ovirt_host_deploy/hardware<wbr>.py", line 134, in _vmx_enabled_by_bios</div><div> self._prdmsr(0, MSR_IA32_FEATURE_CONTROL) & (</div><div> File "/usr/lib/python2.7/site-packa<wbr>ges/ovirt_host_deploy/hardware<wbr>.py", line 121, in _prdmsr</div><div> ret = struct.unpack('L', f.read(8))[0]</div><div>IOError: [Errno 5] Input/output error</div><div>2016-09-13 19:41:52 WARNING otopi.plugins.gr_he_setup.vdsm<wbr>d.cpu cpu._setup:156 Cannot detect if hardware supports virtualization</div></div><div><br></div><div>Can you please check if vmx is enabled in the bios of your host?</div><div>Otherwise vdsm/libvrit will refuse to start the VM.</div><div><div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On 14 September 2016 at 09:59, Simone Tiraboschi <span dir="ltr"><<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 14, 2016 at 10:46 AM, Maton, Brett <span dir="ltr"><<a href="mailto:matonb@ltresources.co.uk" target="_blank">matonb@ltresources.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Log attached as request<br></div><div><div><div class="gmail_extra"><br></div></div></div></blockquote><div><br></div><div>Sorry, I was asking for hosted-engine-setup logs; you can find them under /var/log/ovirt-hosted-en<wbr>gine-setup/</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><div class="gmail_extra"><div class="gmail_quote">On 14 September 2016 at 08:48, Simone Tiraboschi <span dir="ltr"><<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Sep 14, 2016 at 8:19 AM, Maton, Brett <span dir="ltr"><<a href="mailto:matonb@ltresources.co.uk" target="_blank">matonb@ltresources.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div><br></div>I'm having trouble deploying selfhosted engine following this guide <a href="http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/" target="_blank">http://www.ovirt.org/develop/d<wbr>eveloper-guide/engine/migrate-<wbr>to-hosted-engine/</a><br><br></div>It gets close to deploying the vm, but fails with<br><br>2016-09-13 19:46:04 ERROR otopi.plugins.gr_he_common.cor<wbr>e.misc misc._terminate:180 Hosted Engine deployment failed: this system is not reliable, please check the issue,fix and redeploy<br></div></div></div></blockquote><div><br></div></span><div>can you please attach the whole log to let us check where it's failing?</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><br></div>For storage I chose a random NFS share on a remote host that was empty, I did notice that something kept removing 'nameserver' entries from resolv.conf<br><br>vdsm log show issues connecting to the broker,<br></div></div></blockquote><div><br></div></span><div>ovirt-hosted-engine-setup will enable and start the broker if and only if the deployment went fine; that errors at deploy time are harmless since the broker is really down.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span><div dir="ltr"><div><br>periodic/0::ERROR::2016-09-13 19:49:49,704::brokerlink::75::<wbr>ovirt_hosted_engine_ha.lib.bro<wbr>kerlink.BrokerLink::(connect) Failed to connect to broker, the number of errors has exceeded the limit (1)<br>periodic/0::ERROR::2016-09-13 19:49:49,704::api::253::root::<wbr>(_getHaInfo) failed to retrieve Hosted Engine HA info<br>periodic/1::WARNING::2016-09-1<wbr>3 19:49:49,748::periodic::269::v<wbr>irt.periodic.VmDispatcher::(__<wbr>call__) could not run <class 'vdsm.virt.periodic.DriveWater<wbr>markMonitor'> on [u'1ed592d3-2b69-4901-9ff6-fe2<wbr>1d1dff8c5']<br>periodic/2::WARNING::2016-09-1<wbr>3 19:49:51,749::periodic::269::v<wbr>irt.periodic.VmDispatcher::(__<wbr>call__) could not run <class 'vdsm.virt.periodic.DriveWater<wbr>markMonitor'> on [u'1ed592d3-2b69-4901-9ff6-fe2<wbr>1d1dff8c5']<br>periodic/3::WARNING::2016-09-1<wbr>3 19:49:53,749::periodic::269::v<wbr>irt.periodic.VmDispatcher::(__<wbr>call__) could not run <class 'vdsm.virt.periodic.DriveWater<wbr>markMonitor'> on [u'1ed592d3-2b69-4901-9ff6-fe2<wbr>1d1dff8c5']<br>periodic/0::WARNING::2016-09-1<wbr>3 19:49:55,750::periodic::269::v<wbr>irt.periodic.VmDispatcher::(__<wbr>call__) could not run <class 'vdsm.virt.periodic.DriveWater<wbr>markMonitor'> on [u'1ed592d3-2b69-4901-9ff6-fe2<wbr>1d1dff8c5']<br>periodic/1::WARNING::2016-09-1<wbr>3 19:49:57,750::periodic::269::v<wbr>irt.periodic.VmDispatcher::(__<wbr>call__) could not run <class 'vdsm.virt.periodic.DriveWater<wbr>markMonitor'> on [u'1ed592d3-2b69-4901-9ff6-fe2<wbr>1d1dff8c5']<br>periodic/2::WARNING::2016-09-1<wbr>3 19:49:59,751::periodic::269::v<wbr>irt.periodic.VmDispatcher::(__<wbr>call__) could not run <class 'vdsm.virt.periodic.DriveWater<wbr>markMonitor'> on [u'1ed592d3-2b69-4901-9ff6-fe2<wbr>1d1dff8c5']<br><br></div><div>What should I check next ?<br></div></div>
<br></span>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<br></blockquote></div><br></div></div>
</blockquote></div><br></div>
</div></div></blockquote></span></div><br></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div></div></div><br></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div></div></div><br></div></div>
</blockquote></div></div></div><br></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>