Unable to set up host bond networks
Hi We are trying to create a cluster using OLVM 4.5 (with an up to date OEL8 kernel) with a bond of 2 virtual interfaces (mode 2 XOR) that we have set up with NetworkManager prior to adding the KVM host to oVirt. Hosts are added successfully and we can see the two physical NICs (eth0/eth1) in the Setup Host Networks dialog, however the bond0 device is hidden as are the virtual slave interfaces (so we cannot create the bond in oVirt either). It appears the bond0 is sent to oVirt by VDSM as we see it is continually sent in the vdsm log file from the host as well as listed in the capabilities using vdsm-client. We didn't find obvious errors in ovirt-engine.log or in host-deploy or in the vdsm logs on the KVM hosts. We assume there is some validation or filtering oVirt uses that is hiding the bond / slave interfaces and that maybe our slave interfaces are missing some property oVirt wants but we cannot find it in the code in order to work around this - any pointers appreciated. Thanks Erik
Hi Erik, did you try to get the bond interface created by OLVM/oVirt engine ? Are your OL8 systems updated to the latest for all packages ? Simon
On Mar 17, 2025, at 9:18 AM, erik@linux.com wrote:
Hi
We are trying to create a cluster using OLVM 4.5 (with an up to date OEL8 kernel) with a bond of 2 virtual interfaces (mode 2 XOR) that we have set up with NetworkManager prior to adding the KVM host to oVirt.
Hosts are added successfully and we can see the two physical NICs (eth0/eth1) in the Setup Host Networks dialog, however the bond0 device is hidden as are the virtual slave interfaces (so we cannot create the bond in oVirt either).
It appears the bond0 is sent to oVirt by VDSM as we see it is continually sent in the vdsm log file from the host as well as listed in the capabilities using vdsm-client. We didn't find obvious errors in ovirt-engine.log or in host-deploy or in the vdsm logs on the KVM hosts.
We assume there is some validation or filtering oVirt uses that is hiding the bond / slave interfaces and that maybe our slave interfaces are missing some property oVirt wants but we cannot find it in the code in order to work around this - any pointers appreciated.
Thanks
Erik _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!AC... oVirt Code of Conduct: https://urldefense.com/v3/__https://www.ovirt.org/community/about/community-... List Archives: https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovir...
We can't create the bond in oVirt because the slave NICs don't appear in the console. OEL8 is updated to latest. I think the slave NICs are not appearing because they are not physical and there is validation going on that filters them from the UI, but cannot find where that validation is happening in the code.
Update: have learned that the bond0 is listed in the capabilities by vdsm-client, with the correct slave interface name, but the slave interfaces themselves do not appear in the "nics" array, only the physical nics appear here. So there is probably validation in VDSM where it is rejecting the virtual NICs and this is then invalidating the bond in oVirt because oVirt doesn't know about the slaves?
participants (2)
-
erik＠linux.com -
Simon Coter