eth0 not starting on boot after Virtualbox clone

Posted on

Problem :

After cloning my CentOS VM in Virtualbox (I used the Reinitialize the MAC address of all network cards option), the original and the clone VM both now has as their IP.

Anyone knows how to fix it?
The vbox’s IP used to follow my network’s IP (i.e., if host is then the vbox is but now the vboxes is both
I am using Bridged Adapter BTW.

OK, I now realize eth0 is not running on start up. My question now is how enable eth0 on startup? Note that it used to start automatically before I performed the clone.

Solution :

For your this question how enable eth0 on startup?

Open /etc/sysconfig/network-scripts/ifcfg-eth0 file in that

change ONBOOT=no



I just find from on other another site, you need to edit the file name 70-persistent-net.rules under /etc/udev/rules.d/ change the MAC address to match with the clone VM virtualbox

so edit two files

  1. /etc/udev/rules.d/70-persistent-net.rules
  2. /etc/sysconfig/network-scripts/ifcfg-eth0 — from heavyd

change the MAC address in both files to match with the VM VirtualBox assign if you click on the right click cloneVMvirutalBox=>Setting=>Network=>Adapter 1 tap there is a Advanced will provide the MAC address.

Hope this will help when some one come across this site.

CentOS ties the network configuration script to a specific MAC address, so when you changed your MAC address you essentially broke the script. You can fix it by editing the script as root:

sudoedit /etc/sysconfig/network-scripts/ifcfg-eth0

In the script look for the line HWADDR line. Update the value to match your new MAC address and then reboot.

In Virtual Machine settings, remove the network card and reinstall it.
Restart the VM if needed

check your device name with

ip link show

It should work now.

Leave a Reply

Your email address will not be published. Required fields are marked *