“Device eth0 does not seem to be present” – cloned VM’s

24 Nov

This is because when RHEL clones a VM it gives it a new MAC address.

You can see that instead of just eth0 there is eth1 now too by:

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

Two options to fix it:
1. Edit the above file and re-jig the MAC address.
2. Go to /etc/sysconfig/network-scripts and rename the file ifcfg-eth0 to ifcfg-eth1, then edit the file to change reference of eth0 to eth1

Advertisements

4 Responses to ““Device eth0 does not seem to be present” – cloned VM’s”

  1. But I appreciate the article. April 2, 2012 at 4:37 pm #

    Life Saver. Thanks!

  2. Me May 22, 2012 at 3:18 am #

    Another option is to just wipe out the entries from 70-persistent-net.rules and reboot the clone – they will be re-created with the MAC that the host assigns the vm.

  3. xcage November 5, 2012 at 11:02 am #

    thanx its working

  4. Ked January 9, 2014 at 9:04 am #

    Thanks for the pointer, got my cloned KVM LV working 🙂

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: