Thanks for the reply. I figured it out yesterday. I just edited the VM Custom Mac Address and it works like a champ now...I will setup that range and it should be good to go.. I am running oVirt 4.0.. oVirt is a nice product, beats the heck out of Xen Server..On Sun, Sep 25, 2016 at 6:57 AM, Yevgeny Zaspitsky <yzaspits@redhat.com> wrote:YevgenyRegards,You could find MAC-pool definitions under a DC definitions in v4.0 and under a cluster in v4.1.oVirt does not produce IP addresses, but it allocates MAC addresses to vNics on VMs it creates.
A MAC address serves as the base for an IPv6 address allocation (either by IPv6 router advertisement for global addresses or by an operation system for local addresses).
BTW, 2 vNics with the same MAC address in the same LAN, would cause layer 2 (Ethernet) malfunctioning too.
In order to make the 2 oVirt's produce different MAC addresses you need to adjust the definition of the MAC-pool ranges to be non-overlapping each to another.On Sat, Sep 24, 2016 at 5:44 PM, Allen Warren <dallenwarren@gmail.com> wrote:I have two oVirt servers running as local servers on the same network. How do I prevent the servers from creating the same ipv6 address for two different vm's. If I start a vm on the first server and then start one on the second server the ipv6 addresses are the same..
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users