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

By: Lawrence Salmingo

Lawrence Salmingo — Wed, 05 Nov 2008 16:53:57 +0000

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

By: Robert

Robert — Sat, 18 Oct 2008 18:58:50 +0000

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.

By: arab

arab — Sun, 05 Oct 2008 17:07:36 +0000

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

You’re a lifesaver.

By: Stuart Colville

Stuart Colville — Wed, 01 Oct 2008 09:11:58 +0000

@SonniesEdge: Thanks I’ve updated the post

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

By: AlastairC

AlastairC — Sat, 09 Aug 2008 10:37:28 +0000

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.

By: SonniesEdge

SonniesEdge — Tue, 05 Aug 2008 09:12:41 +0000

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.