Package: udev
Version: 0.105-4
Hi.
On VMware ESX Server virtual machines (VM) have virtual NICs with
generated MAC-addresses. These MAC is changing everytime a VM is copied
to another location (e.g. Cloning) or moved to another VMware server
for high availability (HA) or load balancing reasons. There is a
possibility to set a fixed MAC in the VM config file which is not
recommended by VMware because of lost flexibility and probable MAC
collisions.
Therefore it is a problem with the automatic eth{n}-Device generation of
the /lib/udev/write_net_rules script, because it is generating a new
eth{n+1} interface everytime a VM changes its location. As a side
effect the network connection of the VM is broken because the network
configuration in /etc/network/interfaces is for an no longer existing
NIC eth{n}. I think disabling the persistent-net-generator is no
solution for this problem.
There should probably a rule covering VMware network cards. However it
is not a good choice to identify VMware NICs by its MAC address. The
sequence of the NICs should stay the same each time a machine is moved
so that the connection to the virtual switches (connection to the
physical NIC) stays up after VM is moved.
I know this not a problem with udev itself, but it is a big problem for
debian as guest OS on VMware ESX Servers and probable other VMware
Virtualization Products.
Regards
Kai
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
