Problems with network when I copy a Linux VM

[WarlockArg]

Hi,

I noticed that when I copy a powered off VM that runs Suse from an ESX server to another, when I power on the VM in the another ESX server, the Suse Linux keeps remembering as the Eth0 network card the MAC Address of the previous ESX server and it shows a second NIC with the MAC Address of the actual ESX server. Am I doing the copy in a bad way? Is the correct way to make a copy of a VM from an ESX server to another or there is a better one?

Thanks.

[bggb29]

Some versions of linux servers behave strange after copying. I have seen the nic eth0 change to eth 1 etc.

Search for your flavor of linux.

I have fixed a few versions of linux like this

Added a new nic and now it is not seen. Problem occurs with the mac address being hard coded into the following files

/etc/udev/rules.d/70-persistent-net.rules

Delete the above file the system will autogenerate a new file with a new mac upon reboot.

Check to see if this could be your issue. Also I have change from vmxnet to flexible in a few instances to fix a linux box

[AndreTheGiant]

On the same virtual infrastructure cannot exist two running VM with the same MAC address (and VM UUID).

For this reason after the copy (and before the power-on) some information in the vmx will be automatically changed.

As written before, all Linux distro that use udev will detect a new MAC address and build a new eth device.

To avoid this you can clean the relative udev entry before make the copy.

Andre