On Tue, Jan 21, 2020 at 2:30 PM Vrgotic, Marko
While investigating and DHCP & DDNS collision issues between two VM servers from
different oVirt clusters, I noticed that oVirt assigns same default MAC range for each of
it’s managed clusters.
Is this a new 4.3 setup, or upgraded from earlier versions?
Fixed in 4.3 (and backported to 4.2.7), only for new setups. The
default changed several times in versions before these, and upgrades
do not change the stored default.
What's your default mac pool in each engine? You can get it with:
/usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select from_mac,
to_mac from mac_pools, mac_pool_ranges where id=mac_pool_id and
Or by checking admin ui - Administration -> Configure, there "MAC
Address Pools", and double click Default.
Question1: Does oVirt-Engine keep separate place in DB or … for MAC addresses assigned
per cluster or it keeps them all in same place?
By *default*, all in same place, and above bug (and patches linked
from it) describe the current specifics. This changed several times
along the versions before these.
You can manually configure it, including to be per cluster - search
for "MAC Address Pools" here:
Question2: Would there be an harming effect on existing VMs if the default mac pool would
I am pretty certain it's harmless, but didn't try that myself.
Self Hosted ovirt-engine – 4.3.4 and 4.3.7
kind regards/met vriendelijke groeten
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/