Ubuntu and VMware – Losing your ethernet device when migrating
VMWare bases the MAC address of interface on it’s internal UUID. If you shift a machine (copy, rename) vmware asks to update the UUID. You might get something like this:
# ifup eth0
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
SIOCSIFADDR: No such device
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
The solution found by hbraga is to check /etc/iftab. Ubuntu on install adds the MAC address for each interface to this file. Either comment out the lines or update them to reflect the correct details.
Technorati Tags: vmware, ubuntu, network error fix
Mark Said,
April 27, 2007 @ 6:58 am
In Debian Etch, it seems to get confused in a similar way.
The solution is slightly different though – you need to remove the old MAC address entry in
/etc/udev/rules.d/z25_persistent-net.rules
and change the entry for the new MAC address to use eth0 (in my case it became eth1).
Claudio Said,
July 4, 2007 @ 1:40 am
Thank you (both), it solved my problem!
links for 2007-08-21 @ BVLog Said,
August 21, 2007 @ 4:20 pm
[…] Somewhere out there! » Blog Archive » Ubuntu and VMware – Losing your ethernet device when migrati… Solution to Debian VM losing eth0 after moving to a new host. (see comments) (tags: debian virtualmachine vmware sysadmin networking) no comments yet. « links for 2007-08-12 Leave a Comment […]
Psymon101 Said,
September 18, 2007 @ 10:42 am
Thank you!, I have tried to resolve this for a while, I knew it was going to be something small
🙂
YeGods! :: eth0: no such device Said,
September 4, 2008 @ 6:43 am
[…] non ero il primo a ricevere questo errore :-). Nel post si parla di Ubuntu, ma in uno dei commenti viene indicata anche la soluzione per […]
dmooney Said,
October 23, 2008 @ 4:49 am
Ubuntu 8.04 has this setting in /etc/udev/rules.d/70-persistent-net.rules
GiBiLog » Blog Archive eth0: no such device Said,
October 31, 2008 @ 10:59 am
[…] non ero il primo a ricevere questo errore :-). Nel post si parla di Ubuntu, ma in uno dei commenti viene indicata anche la soluzione per […]
felix Said,
December 2, 2008 @ 11:25 pm
thnks a lot Mark
i’ve a similar issue with my debian-VM (in virtualbox) after moving it to another host
and solved editing /etc/udev/rules.d/z25_persistent-net.rules
pikemon Said,
March 4, 2009 @ 3:01 pm
for me nothing helped except
sudo /etc/init.d/udev restart
sudo /etc/init.d/networking restart
this on 8.04 🙂
Tjoa Said,
August 28, 2011 @ 7:22 pm
thanks, works for me.. 🙂
Nicholas Lee Said,
March 6, 2009 @ 4:37 pm
This bug [1] ticket has some detail about the fix as well.
[1] https://bugs.launchpad.net/bugs/289921
The case of the disappearing eth0 @ BVLog Said,
March 12, 2009 @ 3:51 am
[…] A comment on this post pointed me down the path of […]
— Somewhere out there! Said,
March 16, 2009 @ 8:59 am
[…] Professional VMware blog, here is another method to fix your lost Ethernet device on […]
Josep Said,
March 20, 2009 @ 12:53 am
Thanks.
Your post saved my day!
🙂
Alex Said,
April 27, 2009 @ 5:35 am
Simplest solution:
1. edit /etc/network/interfaces and change eth0 to eth1
2. reboot
3. VMWare will auto-generate a new virtual hardware NIC and Linux will auto-configure it.
Tom Said,
January 13, 2010 @ 8:00 am
thanks!
Chris Said,
August 29, 2010 @ 3:02 pm
This was by far the easiest solution to implement. Even the biggest N00b could do it. Thanks. Is there any way to move this solution to the top of the page?????
Mustafa Said,
February 8, 2011 @ 6:18 pm
talking of noobs .!!! I am one 🙁 do i need to edit the file on the host OS or guest ?
Nicholas_Lee Said,
February 21, 2011 @ 1:36 pm
Guest OS.
Jan Said,
May 21, 2009 @ 9:55 pm
Tnx a lot! I was struggling for an hour or so.. while the fix was only 30 secs 😉
Thomas Said,
June 4, 2009 @ 12:10 am
Editing /etc/udev/rules.d/70-persistent-net.rules in 8.10 worked wonders. I had to update my DHCP Reservation on the network with the new MAC Address, but that’s beside the point.
mischa Said,
January 9, 2010 @ 2:10 pm
if you have the new virtualbox, you can set the mac address also in the VM settings of the VM in virtualbox.
so i changed the mac address there instead of inside the VM
Wolfgang Said,
February 10, 2010 @ 8:33 am
Thx Alex, that works!
Napsty Said,
June 5, 2010 @ 11:58 pm
THANKS for that!!!! Was in urgent problems and this solved it!
BoobaSkaya Said,
July 22, 2010 @ 8:58 pm
On ubuntu 10.04, removing lines in /etc/udev/rules.d/70-persistent-net.rules and restarting computer saved me.
Thx all for this kind of support o/
Pietro Said,
September 1, 2010 @ 9:26 pm
Thanks! My /etc/udev/rules.d/70-persistent-net.rules had more lines for same network adapter. I deleted wrong lines, rewrite NAME and reboot.
nick Said,
August 18, 2010 @ 3:43 pm
yes it worked for me as well.
Hussain Said,
September 9, 2010 @ 12:39 pm
Below solution worked for me too on server 10.04
On ubuntu 10.04, removing lines in /etc/udev/rules.d/70-persistent-net.rules and restarting computer saved me.
echessier Said,
October 3, 2010 @ 2:12 am
you just rescued me from a night in purgatory kudos!!!!
ubuntufun Said,
May 31, 2011 @ 5:23 am
great post check out flash flicker
ViperBR Said,
June 23, 2011 @ 2:29 am
On ubuntu 10.04, removing lines in /etc/udev/rules.d/70-persistent-net.rules and restarting computer saved me too. Nice trick.
huso Said,
May 9, 2012 @ 7:26 pm
Below solution worked for me too on server 10.04
On ubuntu 10.04, removing lines in /etc/udev/rules.d/70-persistent-net.rules and restarting computer saved me.
Thanks alot. that solution saved me too. thanks a million….
fatihhayri Said,
July 26, 2012 @ 8:42 pm
On ubuntu 10.04, removing lines in /etc/udev/rules.d/70-persistent-net.rules and restarting computer saved me.
thanx