On Fri, Sep 7, 2018 at 4:04 PM Giuseppe Ragusa <giuseppe.ragusa(a)hotmail.com>
sorry for the late comment (I just found this thread while researching on
nested oVirt-on-VMware issues).
It seems that the problem is generally known and has been solved upstream
in kernel 4.16:
Any ETA on backports in RHEL7? ;-)
(Note: should I open a Bugzilla on kernel package for this?)
Thanks for the accurate report.
Honestly I'm not aware of backport ETA but I'd suggest to file a bug on
product: Red Hat Enterprise Linux 7, component kernel, subcomponent KVM
pointing to the upstream patch.
Not sure if we are still on time for RHEL 7.6.
I seems that Hyper-V would experience the same troubles and I think
making nested-inside-Windows-host work should be deemed fairly important
for demo/trial/lab uses... :-)
In the meanwhile, workarounds have been published for the new
Ansible-based setup flow:
on the other side, I can confirm that with the legacy setup flow (with
option --noansible) adding the following to the answer file avoids the
problem (did not test whether newer types like pc-i440fx-rhel7.2.0 solve it
Da: Simone Tiraboschi <stirabos(a)redhat.com>
Inviato: lunedì 30 luglio 2018 09:20
Oggetto: [ovirt-users] Re: Failed to deploy ovirt engine with
On Mon, Jul 30, 2018 at 6:04 AM Bong Shau Fui <bongsf(a)gmail.com<mailto:
Yes, it's in a nested environment. L0 is vmware esxi 5.5.
I know for sue that a nested kvm env over vmware esxi is still
problematic; kvm over kvm works fine instead.
Users mailing list -- firstname.lastname@example.org<mailto:email@example.com>
To unsubscribe send an email to users-leave(a)ovirt.org<mailto:
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: