Comments on: Vmware: “SIOCSIFADDR: No such device eth0″ after cloning

By: Deek

Deek — Sat, 13 Feb 2010 05:55:11 +0000

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-”

By: Matt

Matt — Wed, 10 Feb 2010 17:27:50 +0000

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

By: Noé Puyal

Noé Puyal — Tue, 09 Feb 2010 10:55:43 +0000

@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 ^-^

By: Stuart Colville

Stuart Colville — Tue, 09 Feb 2010 09:09:31 +0000

@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.

By: Error eth0 después de clonar con VMWare « Cápsulas de palabras

Error eth0 después de clonar con VMWare « Cápsulas de palabras — Tue, 09 Feb 2010 08:38:59 +0000

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

By: Noé Puyal

Noé Puyal — Tue, 09 Feb 2010 08:24:27 +0000

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

By: piva

piva — Wed, 28 Oct 2009 14:51:42 +0000

Worked, thank´s a lot.

By: Matt

Matt — Tue, 27 Oct 2009 21:22:43 +0000

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

By: Vmware: “SIOCSIFADDR: No such device eth0″ after cloning « System Howtos and Tutorials

Wed, 14 Oct 2009 06:13:41 +0000

[...] 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... [...]

By: loydb

loydb — Wed, 08 Jul 2009 20:51:16 +0000

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!