On Wed, Dec 23, 2009 at 4:23 PM, Marco d'Itri <[email protected]> wrote:

> On Dec 24, Robert LeBlanc <[email protected]> wrote:
>
> > Why? If I need to remove or add an adapter, it breaks all the networking.
> I
> Because you are supposed to keep the names stable by an appropriate
> configuration of the virtualization system.
> Creating persistent rules by default would annoy the users of the common
> case (single interface which changes its MAC address).
>
>
I fail to see the logic, by what you are saying is that the same can be
applied to physical machines as well, hence all MACs should be blacklisted.
Are you telling me that the interfaces will always come up in the same order
every time? I had to add an additional adapter and udev inserted it in
between the two existing interfaces. I had no way of knowing that until
after I booted the machine and found that things were not working. I could
either remap all the virtual networking in ESX, or I could write my own
persistent file to keep the adapters where they were. I chose the latter so
I would not be caught off guard again.

I'm not sure what you mean by changing the MAC. The MAC is usually set when
an adapter is created and stays there for the life of the VM, even if it is
moved. The only problem I see is with templates, the solution is easy, trash
the persistent file when a template is cloned. I would prefer to be
inconvienced by trashing the persistent file before a machine goes into
production then have networking meltdown after it is in production.

I'm just trying to understand how the conclusion was reached, it's not
making sense to me yet. I can make my own persistent file, it's just a pain
because I do all of my work in VMs. I did look to see why the file was not
generated and it might be good to include in the README.Debian that certain
MACs are blacklisted and would not be included in the persistent file. What
may even be good, if possible, is to set something in /etc/default/ to
choose whether or not to blacklist VM MACs.

Thanks,

Robert LeBlanc
Life Sciences & Undergraduate Education Computer Support
Brigham Young University

Reply via email to