Knowledgebase: Using your AirVM
Why is my eth0 device missing after cloning my linux VM
Posted by Jazmine Burke on 27 July 2012 11:16 AM
When you clone a VMware virtual machine, the new virtual machine’s network interface gets a new MAC address. But many Linux distributions, cache the old MAC address in a configuration file.

In some Linux distributions, the file is /etc/udev/rules.d/70-persistent-net.rules (Ubuntu), /etc/udev/rules.d/z25_persistent-net.rules (Debian). After cloning, it will contain a reference to the old network interface as eth0.


The easiest way to fix this problem is to simply delete the file. Linux will regenerate it properly the next time it boots up.


#bash: rm /etc/udev/rules.d/70-persistent-net.rules


After deleting the file, you need to reboot. After rebooting, ifconfig should show eth0 and everything should just work.

If you’re feeling less adventurous, you can rename the file to *.old so that you can restore it if something doesn’t work:


#bash: mv /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/70-persistent-net.rules.old


You can also edit the file to remove the old reference to eth0, and rename the new eth1 reference to eth0.

The relevant filename is slightly different in other Linux distributions.

(0 votes)
This article was helpful
This article was not helpful

Comments (0)
Post a new comment 
Full Name:
Help Desk Software by Kayako Fusion