Hi, No, oVirt isn't aware of config changes - it's by design, not a bug. You always have to restart engine when changing values (as noted in engine-config help text). # engine-config -h <snip> ### 2. In order for your change(s) to take effect, ### restart the oVirt engine service (using: 'service ovirt-engine restart'). Regards, René On Fri, 2013-05-17 at 13:57 +0200, noc wrote:

Hi All,

Don't know if this is documented somewhere but I ran into an interesting problem yesterday. First we had intermittent problems with ssh connecting to VMs which we traced to having two oVirt installation being active in one subnet. Found the post from January where it is explained how engine allocates its mac address pool and how to set it with engine-config -s MacPoolRanges. Today I remembered that I had done that when I was about to start a VM and removed the nic from the VM and added it back. To my surprise it got the same macaddress as it had (from the old range). On a hunch I restarted ovirt-engine and redid the remove/add operation and now it got a new mac address from the range specified. Shouldn't the engine be aware that the config is changed if you use engine-config and reload its cached values from the database? I expected this but it seems not to be the case, bug or by design.

Joop

-- irc: jvandewege

_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users