On Fri, May 24, 2019 at 3:39 PM <[email protected]> wrote: > El 2019-05-24 14:30, Simone Tiraboschi escribió: > > On Fri, May 24, 2019 at 2:56 PM <[email protected]> wrote: > > > >> El 2019-05-24 13:39, Simone Tiraboschi escribió: > >>> On Fri, May 24, 2019 at 2:32 PM <[email protected]> wrote: > >>> > >>>> El 2019-05-24 13:22, Simone Tiraboschi escribió: > >>>>> On Fri, May 24, 2019 at 1:51 PM <[email protected]> wrote: > >>>>> > >>>>>> El 2019-05-24 12:41, [email protected] escribió: > >>>>>>> El 2019-05-14 08:19, Yedidyah Bar David escribió: > >>>>>>>> On Tue, May 14, 2019 at 10:02 AM <[email protected]> wrote: > >>>>>>>>> > >>>>>>>>> Please, any ideas about this? > >>>>>>>>> > >>>>>>>>> Thanks. > >>>>>>>>> > >>>>>>>>> El 2019-05-10 09:18, [email protected] escribió: > >>>>>>>>> > Hi, > >>>>>>>>> > > >>>>>>>>> > We're running oVirt version 4.3.3, and trying to > >> configure > >>>>>> one of the > >>>>>>>>> > hosts to support Nested Virtualization, but when > >> installing > >>>>>> the nested > >>>>>>>>> > host it claims it doesn't support hardware > >> virtualization. > >>>>>>>>> > > >>>>>>>>> > On the physical host, we've enabled nested > >> virtualization: > >>>>>>>>> > > >>>>>>>>> > # cat /sys/module/kvm_intel/parameters/nested > >>>>>>>>> > Y > >>>>>>>>> > > >>>>>>>>> > Content of /etc/modprobe.d/kvm.conf: > >>>>>>>>> > > >>>>>>>>> > options kvm_intel nested=1 > >>>>>>>>> > options kvm_intel enable_shadow_vmcs=1 > >>>>>>>>> > options kvm_intel enable_apicv=1 > >>>>>>>>> > options kvm_intel ept=1 > >>>>>>>>> > > >>>>>>>>> > I created a VM to run on that host, which will be the > >>>> nested > >>>>>> host. I > >>>>>>>>> > try to deploy it but the engine will show it failed > >>>> because: > >>>>>>>>> > > >>>>>>>>> > 2019-05-10 09:11:32,006+01 ERROR > >>>>>>>>> > > >>>>>> > >>>>> > >>>> > >>> > >> > > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > >>>>>>>>> > (VdsDeploy) [6381e662] EVENT_ID: > >>>>>> VDS_INSTALL_IN_PROGRESS_ERROR(511), > >>>>>>>>> > An error has occurred during installation of Host host1: > >>>>>> Failed to > >>>>>>>>> > execute stage 'Setup validation': Hardware does not > >> support > >>>>>>>>> > virtualization. > >>>>>>>> > >>>>>>> > >>>>>>> Hi Yedidyah, sorry for the delayed answer. > >>>>>>> > >>>>>>>> You might find some more details in the host-deploy log, > >>>>>>>> which you should be able to find in > >>>>>> /var/log/ovirt-engine/host-deploy > >>>>>>>> (on the engine machine, it's copied there after deploy > >>>>>> finishes). > >>>>>>>> > >>>>>>> > >>>>>>> I had a look at it, but nothing relevant shows up besides > >> this > >>>>>> line: > >>>>>>> > >>>>>>> 2019-05-10 09:11:32,628+0100 DEBUG otopi.context > >>>>>>> context._executeMethod:145 method exception > >>>>>>> Traceback (most recent call last): > >>>>>>> File "/tmp/ovirt-qPjYkVy6Ys/pythonlib/otopi/context.py", > >>>> line > >>>>>> 132, > >>>>>>> in _executeMethod > >>>>>>> method['method']() > >>>>>>> File > >>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > > "/tmp/ovirt-qPjYkVy6Ys/otopi-plugins/ovirt-host-deploy/vdsm/hardware.py", > >>>>>>> line 71, in _validate_virtualization > >>>>>>> _('Hardware does not support virtualization') > >>>>>>> RuntimeError: Hardware does not support virtualization > >>>>>>> > >>>>>>>> It's been some time since I configured this myself, so I do > >>>> not > >>>>>>>> remember > >>>>>>>> the details anymore. Did you check some guides/blog > >> posts/etc. > >>>>>> about > >>>>>>>> this? > >>>>>>>> > >>>>>>> > >>>>>>> I didn't. I just enabled nested virtualization in the host > >> and > >>>>>> tried to > >>>>>>> deploy. > >>>>>>> > >>>>>>>> What type of CPU did you configure in the VM (and cluster)? > >>>>>>>> > >>>>>>> > >>>>>>> In the Cluster I have the Intel Broadwell Family, and as the > >> VM > >>>>>> CPU I > >>>>>>> have the default cluster CPU which is the one I just > >>>> referenced. > >>>>>> Not > >>>>>>> sure if anything else should be done. > >>>>>>> > >>>>>>>> To see what checks the code does, you can read [1], although > >>>> the > >>>>>> log > >>>>>>>> should be enough IMO. > >>>>>>>> > >>>>>>>> [1] > >>>>>> /usr/lib/python2.7/site-packages/ovirt_host_deploy/hardware.py > >>>>>> > >>>>>> I just saw this in the log: > >>>>>> > >>>>>> 2019-05-24 12:44:56,000+0100 DEBUG > >>>> otopi.ovirt_host_deploy.hardware > >>>>>> > >>>>>> hardware._isVirtualizationEnabled:208 virtualization support > >>>>>> GenuineIntel (cpu: False, bios: True) > >>>>>> > >>>>>> So the CPU is not able to support virtualization. Why could be > >>>>>> that? > >>>>> > >>>>> Hi, > >>>>> can you please share the output of cat /proc/cpuinfo ? > >>>>> > >>>> > >>>> Hi Simone, > >>>> > >>>> Please find attached the output (assuming you meant the VM that > >> is > >>>> meant > >>>> to be added as a host). You'll probably see the model name as > >>>> Haswell > >>>> because I forced it to test, but the same happens with > >> Broadwell. > >>> > >>> OK, > >>> vmx flag is not there so this VM doesn't support virtualization > >> and > >>> for that you have to enable nested virt support on the underlying > >>> level. What (SW) are you using on the underlying layer? > >>> > >>> Let's try to recap: > >>> L0 is your physical machine > >>> L1 is the VM you are going to use as a virtualization host for > >> oVirt > >>> L2 are the VM you are going to create with oVirt > >>> > >>> In order to be able to start a L2 VM from oVirt, you have to > >> enable > >>> nested virtualization support on your L0 physical host. > >>> > >> > >> Ok, the output I sent in the previous e-mail was for L1. For L0 I'm > >> > >> sending the cpuinfo log now. > >> > >> I saw in the code, the flag that is returning false at deployment > >> of L1 > >> is this: > >> > >> cpu_ok = self._cpu_has_vmx_support() > >> > >> Which calls the _cpu_has_vmx_support(): > >> > >> def _cpu_has_vmx_support(self): > >> eax, ebx, ecx, edx = self._cpuid(1) > >> # CPUID.1:ECX.VMX[bit 5] -> VT > >> ret = ecx & (1 << 5) != 0 > >> self.logger.debug('vmx support: %s', ret) > >> return ret > >> > >> From that, am I assuming well that vmx support should be enabled > >> also > >> for L1? If so, what could be the reason for not being enabled? > > > > Nested virtualization support on L0 is supposed to enable > > virtualization support (vmx flag) on L1. > > How you defined and started your L1 VMs? > > > > I basically created the L1 VM when L0 had no nested support yet, I > enabled the nested support once the L1 machine was already created, can > that make a difference? >
I suppose so. But which kind of software are you using on your L0? directly libvirt with virsh? virt-install? virt-manager? another oVirt isntance? > > I defined the VM like any other, just with one special option enabled: > to be run on the L0 host which has the nested support enabled. I also > tried shutting down the VM and starting it again, but made no > difference. > > > > >> Thanks again. > >> > >>> > >>> > >>>> Thanks. > >>>> > >>>>> > >>>>>>>> > >>>>>>>> Best regards, > >>>>>>>> > >>>>>>>>> > > >>>>>>>>> > Am I missing something here? > >>>>>>>>> > > >>>>>>>>> > Thanks. > >>>>>>>>> > _______________________________________________ > >>>>>>>>> > Users mailing list -- [email protected] > >>>>>>>>> > To unsubscribe send an email to [email protected] > >>>>>>>>> > Privacy Statement: > >>>> https://www.ovirt.org/site/privacy-policy/ [1] [1] > >>>>>> [1] > >>>>>>>>> > oVirt Code of Conduct: > >>>>>>>>> > > >> https://www.ovirt.org/community/about/community-guidelines/ [2] > >>>> [2] > >>>>>> [2] > >>>>>>>>> > List Archives: > >>>>>>>>> > > >>>>>> > >>>>> > >>>> > >>> > >> > > > https://lists.ovirt.org/archives/list/[email protected]/message/P7ZJB2NVO5DYARQTEHLMA4WR3T3P6N4N/ > >> [3] > >>>> [3] > >>>>>> [3] > >>>>>>>>> _______________________________________________ > >>>>>>>>> Users mailing list -- [email protected] > >>>>>>>>> To unsubscribe send an email to [email protected] > >>>>>>>>> Privacy Statement: > >> https://www.ovirt.org/site/privacy-policy/ [1] > >>>> [1] > >>>>>> [1] > >>>>>>>>> oVirt Code of Conduct: > >>>>>>>>> https://www.ovirt.org/community/about/community-guidelines/ > >> [2] > >>>> [2] [2] > >>>>>>>>> List Archives: > >>>>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > > > https://lists.ovirt.org/archives/list/[email protected]/message/7LALMJF4SQQXLFZUXV2I53YRGX7J7FR6/ > >> [4] > >>>> [4] > >>>>>> [4] > >>>>>>> _______________________________________________ > >>>>>>> Users mailing list -- [email protected] > >>>>>>> To unsubscribe send an email to [email protected] > >>>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > >> [1] > >>>> [1] [1] > >>>>>>> oVirt Code of Conduct: > >>>>>>> https://www.ovirt.org/community/about/community-guidelines/ > >> [2] [2] > >>>> [2] > >>>>>>> List Archives: > >>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > > > https://lists.ovirt.org/archives/list/[email protected]/message/4QMYFBJUMSO7XF2XID4UWY27RMKDV6C4/ > >> [5] > >>>> [5] > >>>>>> [5] > >>>>>> _______________________________________________ > >>>>>> Users mailing list -- [email protected] > >>>>>> To unsubscribe send an email to [email protected] > >>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > >> [1] > >>>> [1] [1] > >>>>>> oVirt Code of Conduct: > >>>>>> https://www.ovirt.org/community/about/community-guidelines/ > >> [2] [2] > >>>> [2] > >>>>>> List Archives: > >>>>>> > >>>>> > >>>> > >>> > >> > > > https://lists.ovirt.org/archives/list/[email protected]/message/6O7QPVYUHVE7BHHSOVRATSYWJA732RPF/ > >> [6] > >>>> [6] > >>>>>> [6] > >>>>> > >>>>> -- > >>>>> > >>>>> Simone Tiraboschi > >>>>> > >>>>> He / Him / His > >>>>> > >>>>> Principal Software Engineer > >>>>> > >>>>> Red Hat [7] > >>>>> > >>>>> [email protected] > >>>>> > >>>>> @redhatjobs [8] redhatjobs [9] @redhatjobs [10] > >>>>> > >>>>> [11] > >>>>> > >>>>> [12] > >>>>> > >>>>> > >>>>> > >>>>> Links: > >>>>> ------ > >>>>> [1] https://www.ovirt.org/site/privacy-policy/ [1] [1] > >>>>> [2] https://www.ovirt.org/community/about/community-guidelines/ > >> [2] > >>>> [2] > >>>>> [3] > >>>>> > >>>> > >>> > >> > > > https://lists.ovirt.org/archives/list/[email protected]/message/P7ZJB2NVO5DYARQTEHLMA4WR3T3P6N4N/ > >> [3] > >>>> [3] > >>>>> [4] > >>>>> > >>>> > >>> > >> > > > https://lists.ovirt.org/archives/list/[email protected]/message/7LALMJF4SQQXLFZUXV2I53YRGX7J7FR6/ > >> [4] > >>>> [4] > >>>>> [5] > >>>>> > >>>> > >>> > >> > > > https://lists.ovirt.org/archives/list/[email protected]/message/4QMYFBJUMSO7XF2XID4UWY27RMKDV6C4/ > >> [5] > >>>> [5] > >>>>> [6] > >>>>> > >>>> > >>> > >> > > > https://lists.ovirt.org/archives/list/[email protected]/message/6O7QPVYUHVE7BHHSOVRATSYWJA732RPF/ > >> [6] > >>>> [6] > >>>>> [7] https://www.redhat.com/ [7] [7] > >>>>> [8] https://twitter.com/redhatjobs [8] [8] > >>>>> [9] https://www.facebook.com/redhatjobs [9] [9] > >>>>> [10] https://instagram.com/redhatjobs [10] [10] > >>>>> [11] https://red.ht/sig [11] [11] > >>>>> [12] https://redhat.com/summit [12] [12] > >>> > >>> -- > >>> > >>> Simone Tiraboschi > >>> > >>> He / Him / His > >>> > >>> Principal Software Engineer > >>> > >>> Red Hat [7] > >>> > >>> [email protected] > >>> > >>> @redhatjobs [8] redhatjobs [9] @redhatjobs [10] > >>> > >>> [11] > >>> > >>> [12] > >>> > >>> > >>> > >>> Links: > >>> ------ > >>> [1] https://www.ovirt.org/site/privacy-policy/ [1] > >>> [2] https://www.ovirt.org/community/about/community-guidelines/ > >> [2] > >>> [3] > >>> > >> > > > https://lists.ovirt.org/archives/list/[email protected]/message/P7ZJB2NVO5DYARQTEHLMA4WR3T3P6N4N/ > >> [3] > >>> [4] > >>> > >> > > > https://lists.ovirt.org/archives/list/[email protected]/message/7LALMJF4SQQXLFZUXV2I53YRGX7J7FR6/ > >> [4] > >>> [5] > >>> > >> > > > https://lists.ovirt.org/archives/list/[email protected]/message/4QMYFBJUMSO7XF2XID4UWY27RMKDV6C4/ > >> [5] > >>> [6] > >>> > >> > > > https://lists.ovirt.org/archives/list/[email protected]/message/6O7QPVYUHVE7BHHSOVRATSYWJA732RPF/ > >> [6] > >>> [7] https://www.redhat.com/ [7] > >>> [8] https://twitter.com/redhatjobs [8] > >>> [9] https://www.facebook.com/redhatjobs [9] > >>> [10] https://instagram.com/redhatjobs [10] > >>> [11] https://red.ht/sig [11] > >>> [12] https://redhat.com/summit [12] > > > > -- > > > > Simone Tiraboschi > > > > He / Him / His > > > > Principal Software Engineer > > > > Red Hat [7] > > > > [email protected] > > > > @redhatjobs [8] redhatjobs [9] @redhatjobs [10] > > > > [11] > > > > [12] > > > > > > > > Links: > > ------ > > [1] https://www.ovirt.org/site/privacy-policy/ > > [2] https://www.ovirt.org/community/about/community-guidelines/ > > [3] > > > https://lists.ovirt.org/archives/list/[email protected]/message/P7ZJB2NVO5DYARQTEHLMA4WR3T3P6N4N/ > > [4] > > > https://lists.ovirt.org/archives/list/[email protected]/message/7LALMJF4SQQXLFZUXV2I53YRGX7J7FR6/ > > [5] > > > https://lists.ovirt.org/archives/list/[email protected]/message/4QMYFBJUMSO7XF2XID4UWY27RMKDV6C4/ > > [6] > > > https://lists.ovirt.org/archives/list/[email protected]/message/6O7QPVYUHVE7BHHSOVRATSYWJA732RPF/ > > [7] https://www.redhat.com/ > > [8] https://twitter.com/redhatjobs > > [9] https://www.facebook.com/redhatjobs > > [10] https://instagram.com/redhatjobs > > [11] https://red.ht/sig > > [12] https://redhat.com/summit > -- Simone Tiraboschi He / Him / His Principal Software Engineer Red Hat <https://www.redhat.com/> [email protected] @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://red.ht/sig> <https://redhat.com/summit>
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/CSSCP2DNRCRKOOTJKCCYQSIFNFBBUEOW/
