eth0 dissapear after cloning

I've just cloned a working VM (running debian, using shared networking, static address) but the new VM has problems when trying to configure eth0: it claims there is no such device. My /etc/network/interfaces file looks like this:

Code:

allow-hotplug eth0
iface eth0 inet dhcp

I also tried setting the interface to static and configuring the address, but got the same result. Any ideas why this could be happening?
thanks for any tip.

 

Are you running the original VM?
Also please try to change MAC address for cloned VM

 

No, I was not running the original VM, and yes, I did check that the MAC address of the new VM is different from the original
still no luck though...
At first I thought that it might have happened because I copied the original VM while it was running, so I deleted my clone, stopped the original VM, copied and it happened the same.
The guest OS is Debian Linux (etch) and I'm running the latest version of parallels (build 5608).

 

Ok, try to remove interface while VM is stopped, start and stop Vm, add new interfaces and check

 

nop... that didn't work either :'(
At this point, it would've been better to just start a new VM from scratch, but that was not the idea... maybe if I create a new one and manually copy the disk from the other VM (that is, a "manual cloning" )...

(... checking... )

nope... apparently the problem is debian, because the same thing happens in VMware:

http://communities.vmware.com/thread/83063

Anyway, the tip in the post also worked for me, now I have my eth0 back

 

Just one question for future reference, did you have 2 interfaces, and which tip you used,
Create new one, or replacing eth1 as eth0?

 

I had only 1 interface. udev created a new interface (eth1), so I deleted the (old) interface and renamed eth1 as eth0 in the persistent-net.rules file.

 

Thank you for provided information

 

The following information is correct for Debian Etch (4.0) which uses udev, I don't know if there are other configurations or what the case is for other distros.

The easiest and probably most correct way to fix this issue is to edit /etc/udev/rules.d/z25_persistent-net.rules and remove the problematic entry.

On my system I removed the following entry, rebooted (maybe an "/etc/init.d/networking restart" would be enough) and the problem was resolved.