# Ubuntu
sudo mv /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/70-persistent-net.rules.old

#Debian
sudo mv /etc/udev/rules.d/z25_persistent-net.rules /etc/udev/rules.d/z25_persistent-net.rules.old

# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0c:29:50:xx:xx", ATTR{type}=="1", NAME="eth0"

# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0c:29:36:xx:xx", ATTR{type}=="1", NAME="eth1"

# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0c:29:36:xx:xx", ATTR{type}=="1", NAME="eth0"

Comments: Add yours

1. On August 5th, 2008 at 9:12 am SonniesEdge said:

I’ve found that it’s a lot easier to just delete 70-persistant-net.rules and then reboot the newly-cloned machine. Ubuntu will recreate the file with no problem.

2. On August 9th, 2008 at 10:37 am AlastairC said:

I think this may also help if you transfer a VM from OSX fusion to windows VMware player. I haven’t testing it yet, but I had trouble with eth0 when trying an debian VM on windows.

3. On October 1st, 2008 at 9:11 am Stuart Colville said:

@SonniesEdge: Thanks I’ve updated the post

@AlastairC: Yep indeed this does work for VMWare Fusion I’ve just had exactly that error with Debian.

4. On October 5th, 2008 at 5:07 pm arab said:

Thanks! Saved me a lot of trouble. I had the same problem after cloning one machine.

You’re a lifesaver.

5. On October 18th, 2008 at 6:58 pm Robert said:

Thanks a bunch. Great and precise post that saved me a lot of trouble. I encountered this problem after moving a Virtual Machine from a Windows VMWARE Server 2 environment to a Ubuntu Linux environment.

6. On November 5th, 2008 at 4:53 pm Lawrence Salmingo said:

Thanks so much! Tip #1 Saved my image as I am about to … good thing you had it here! will link this to my site

7. On December 10th, 2008 at 2:04 pm Ragnar said:

Thank you, the Deb mv saved my day

8. On January 28th, 2009 at 7:15 pm Ian Hailey said:

Many thanks for this, I owe you a beer!

9. On January 29th, 2009 at 10:58 pm modah said:

Thanks !!!!!

10. On February 2nd, 2009 at 6:53 pm whall said:

Any tips on what to do if you remove/move the file and it does NOT rebuild it?

In my case, I installed a new VA-LAMP from virtualappliances.net. I did some config and customization
- installed rcconf
- disabled apache, lighthttpd, mysql, php
- changed root password
- shutdown

then I used vmware converter to create a new .OVF locally on my PC. Then I used vmware converter to re-upload the .OVF and create a new image with a new name.

now there’s no eth0. I tried uninstalling/reinstalling vmware tools, removing the persistent-net.rules file, rebooting, removing and re-adding the network card from ESXi and I still can’t get any network on the box.

dmesg shows no eth0 or eth1 lines.

I wonder if it’s a MAC address problem because it came from and went to the same ESXi box, but I’m not sure how to troubleshoot that.

11. On February 17th, 2009 at 7:22 pm Santa said:

This really helped me! Thanks thousandtimes. For others, my configuration: Windows XP running on AMD Athlon 64, Ubuntu server 7.10 running on vmware player.

12. On March 29th, 2009 at 9:36 am Duncan Bayne said:

Thank you, thank you, thank you! My configuration: Ubuntu 8.04 Server LTS running on VMWare Desktop 6.0.

13. On July 8th, 2009 at 8:51 pm loydb said:

Thanks for this, saved my sanity. I moved a Workstation 6.5 VM (latest Ubuntu) from my desktop to my laptop, and eth0 and eth1 stopped working. I deleted the rules file, and everything was fine after a reboot!

14. On October 14th, 2009 at 6:13 am Vmware: “SIOCSIFADDR: No such device eth0″ after cloning « System Howtos and Tutorials said:

[...] Ubuntu : View interface: ifconfig -a Edit /etc/udev/rules.d/70-persistent-net.rules. Ref: http://muffinresearch.co.uk/archives/2008/07/13/vmware-siocsifaddr-no-such-device-eth0-after-cloning... [...]

15. On October 27th, 2009 at 9:22 pm Matt said:

This worked great for me also. Ubuntu 8.10/Esxi 3.5-U4
Just because I’m curious, I’m wondering if there’s a way to get rid of the resulting error message that now comes up during startup:

cifs vfs: error connecting to ipv4 socket. aborting operation
cifs vfs: cifs_mount failed w/return code = -113

16. On October 28th, 2009 at 2:51 pm piva said:

Worked, thank´s a lot.

17. On February 9th, 2010 at 8:24 am Noé Puyal said:

Good morning Stuart
Your post has been the most helpful one I’ve found about my issue, even between the official vmware forums. I would like to translate your post for those who understand spanish in my blog. Do you give me your permission?
Thanks

18. On February 9th, 2010 at 8:38 am Error eth0 después de clonar con VMWare « Cápsulas de palabras said:

[...] http://muffinresearch.co.uk/archives/2008/07/13/vmware-siocsifaddr-no-such-device-eth0-after-cloning... Dejar un comentario [...]

19. On February 9th, 2010 at 9:09 am Stuart Colville said:

@Noé Puyal – You’d be more than welcome! Let me have the link when you’ve done it and I’ll link to it from here.

20. On February 9th, 2010 at 10:55 am Noé Puyal said:

@Stuart Colville – I’ve just finished translating the guide, the url is the trackback from Cápsulas de Palabras -> http://capsulasdepalabras.wordpress.com/2010/02/09/error-eth0-despues-de-clonar-con-vmware/
Thanks for your help and your quick response ^-^

21. On February 10th, 2010 at 5:27 pm Matt said:

Thanks son much for your post, i experienced this exact problem when cloning a Ubuntu 9.04 VM on VMware workstation 6.5

22. On February 13th, 2010 at 5:55 am Deek said:

READ THIS VMUSERS!!!
You can all any e1000 network card to be assigned to eth0. This makes for easy configuration when copying vmsessions.

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

remove this part completly save and reboot:
ATTR {address}==”00:0c:29:30:xx:xx”,

OLD:
SUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR
{address}==”00:0c:29:30:xx:xx”, ATTR{type}==”1″, NAME=”eth0″

NEW:
SUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{type}==”1″, NAME=”eth-”

23. On July 14th, 2010 at 8:22 pm Pål Andreassen said:

Thank you very much. This is just as relevant today as it was in 2008. Had huge problems with eth0 not working after cloning an Ubuntu 10.04 VM in ESXi 4.1. Your post saved me from hours of pain.

24. On August 16th, 2010 at 10:28 pm Chris Markle said:

Wanted to add my two bits that this post is still accurate, relevant and fixed my issue. Specifically I had used the VMware Converter to move an Ubuntu VM from one ESXI machine to another. When I booted the new copy I got something along the lines of “SIOCSIFADDR no such device: eth1″. My /etc/network/interfaces on the original system called for lo and eth1 to be brought up. Per this posting, I deleted /etc/udev/rules.d/70-persistent-net.rules and rebooted. Still didn’t quite work as Ubuntu decided that the ethernet interface was eth2. So I just edited the newly-created /etc/udev/rules.d/70-persistent-net.rules and changed eth2 to eth1, rebooted and all was well. (I could have just as well changed /etc/network/interfaces to use eth2 vs. eth1…). Anyway, thanks for the helpful (and still accurate) post.

25. On August 27th, 2010 at 8:52 am Maynata said:

10x Dude! You’re the MAN ))