Search This Blog

Sunday, December 2, 2012

Device eth0 does not seem to be present after move copy VM

Device eth0 does not seem to be present, delaying initialization. [FAILED]

Got this message after copy a VM to another location.

What I am trying to do is clone a VM.

This happens under VMWare ESXi 5 and other products.

The reason is VMWare gave the VM you moved or copied one for few new NIC.

If check the file: /etc/udev/rules.d/70-persistent-net.rules

You will found the old NIC eth0 still there and the new NIC becomes eth1 etc...

But the eth0 does not exist anymore.

This is a safe protect by RED HAT.

To fix this issue, my solution:

# rm -f /etc/udev/rules.d/70-persistent-net.rules
# reboot


The 70-persistent-net.rules will be generate automatic after reboot.

Then just modify /etc/sysconfig/network-scripts/ifcfg-ethx 's MAC
You are back!

6 comments:

  1. Great write-up, I am a big believer in commenting on blogs to assist the weblog writers know that they’ve added one thing worthwhile to the world large net!Anyway, in my language, there aren’t a lot good source like this.i Will used it again.

    ReplyDelete
  2. it's very useful to me, thank you very much!

    ReplyDelete
  3. Hi My friend,

    Glade this helps.
    But I do not know any other blog or website has same subjects.

    VMware community is a good place to ask question.

    Best Regards,

    ReplyDelete
  4. Good post, it just worked! Thanks

    ReplyDelete
  5. Glade it helps.

    ReplyDelete