vmware clone 之后找不到eth0的解决办法

hillpig

最近在vmare6.0里面clone lfs6.3系统（其他linux系统类似）后，发现clone后的eth0找不到，解决办法如下：
其中这里 http://communities.vmware.com/thread/46069 有充分的讨论：
Hi,
your problems sound exactly like the problem we ran into when cloning a Debian installation.
The root of the problem at our site was udev's handling of devices.
Udev keeps a history of devices attached to the computer. What makes
sense for i.e. USB sticks (that is, each USB stick you attach will be
recorded and mounted to the same point when attached again at a later
point in time), causes problems when systems are cloned.
There is a file /etc/udev/rules.d/z25_persistent-net.rules, where udev
memorises, which hardware device should get named eth0. Here it looks
like this:
# PCI device 14xx:16xx (tg3)
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", SYSFS{address}=="00:11:xx:xx:xx:xx", NAME="eth0"
When you run the image on another computer, the new network adapter is
recognised on the PCI bus and a new entry in the above mentioned file
is generated. "eth0" is already given to device 14xx:16xx, so the new
device gets named "eth1".
If you delete this file, it will be rebuilt during the next system startup and your problem should go away.
Regards,
Rainer
                           
                           
                           
                           
我采用的办法是删除：/etc/udev/rules.d/70-persistent-net-rules
重启就可以了
注意：/etc/udev/rules.d/70-persistent-net-rules 是根据 /etc/udev/rules.d/75-persistent-net-generator-rules自动生成的。
               
               
               

本文来自ChinaUnix博客，如果查看原文请点：http://blog.chinaunix.net/u2/81513/showart_1308973.html