With this comment, I'm poking at getting the engine to run directly on the
node. I figure worst case, I might try throwing it in a container if there's
package conflicts. That'll at least give me the lighter-engine I'm looking for,
along with not having to manage it's resources.
Looks like the
Hi,
> ... You might want to check the list archives for previous discussions about
> this ...
Thanks for those links! I have an idea for a path forward, but I'm not sure
it's supported. It looks like oVirt used to have a "all-in-one" option, but the
hosted engine replaced that.
> I'd like to
Hi,
Is your migration network provisionned by DHCP?
If so, there is a known bug that prevents NetworkManager to set ip rule
table for your migration network, and it won't be fixed before 4.5 release.
As a workaround, you can set the protocol to static or manually assign
rule table to 0 as fo
Hi,
we are trying to upgrade 4.3.7 -> 4.4.9 (Ovirt-Node, hosted engine). And
things looks good until we try to migrate VM from 4.3.7 host to the
4.4.9 host, it fails with an generic error - and in below is from the
vsdm.log from the 4.3.7 host.
Migrating VM from 4.4.9 host -> 4.3.7 host work
I would like to add that I'm getting the same issue but the VM imports. I'm
trying to import the VM from Veeam to enable RHEV native backups. I would LOVE
to get this feature going!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email
5 matches
Mail list logo