This is not my first time, I have installed ovirt, ovirt-hci, rhv and
rhv-hci on top of a kvm host many times to test some functionality or to
test a new version til this latest version of ovirt 4.4.1
On my first test there was a problem with HCI deployment the gluster part.
Now that part works with the new ovirt-node version but not the vm manager
Le jeu. 30 juil. 2020 14:56, Strahil Nikolov via Users <users(a)ovirt.org> a
I've run KVM VMs ontop oVirt Guest. Are you sure that the
Virtualization is your problem ?
На 29 юли 2020 г. 23:33:48 GMT+03:00, thomas(a)hoberg.net написа:
>I tried using nested virtualization, too, a couple of weeks ago.
>I was using a 3 node HCI CentOS 7.8 cluster and I got pretty far.
>Configuring KVM to work with nested page tables isn't all that well
>documented but I got there, I even installed some host extensions, that
>Even the actual nesting, that is a VM run inside a VM did work, the
>setup came to the point where it ran the hosted engine on temporary
>local storage, before it's picked up, fixed up to run on the Gluster
>storage and restarted there. But that process failed eventually,
>evidently because the overlay network doesn't support nesting. Where
>the initial hosted engine is using a local bridge with the (in this
>case virtual) host--and that works--afterwards it's using the overlay
>network and that evidently doesn't.
>It was only then when I ran across a very obscure message somewhere in
>this mailing list, that oVirt on top of oVirt in fact does not work at
>all! Up to that point it just wasn't "supported".
>When a hypervisor producer speaks of nested virtualization support, I
>would understand it to mean that you can run their product under their
>product, ideally also somebody else's product. I've run ESX on VMware
>workstation and that was pretty cool.
>In the case of oVirt from what I have gathered (and I'd love to be
>wrong), it is supposed to only mean that you can run oVirt on top of
>Not the other way around, nor in any other way most likely.
>To me that looks much more like an internal Redhat development
>facility, than a product feature.
>Of course I mostly wish they'd find a way to make it work like it does
>But next on my wishlist would be an explicit description of what does
>and what doesn't work.
>This way it was almost a week of a me against the computer adventure
>where I lost.
>Users mailing list -- users(a)ovirt.org
>To unsubscribe send an email to users-leave(a)ovirt.org
>Privacy Statement: https://www.ovirt.org/privacy-policy.html
>oVirt Code of Conduct:
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: