eth0 not starting on boot after Virtualbox clone
Solution 1
For your this question how enable eth0 on startup?
Open /etc/sysconfig/network-scripts/ifcfg-eth0
file in that
change ONBOOT=no
To
ONBOOT=yes
Solution 2
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
- /etc/udev/rules.d/70-persistent-net.rules
- /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.
Solution 3
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.
Related videos on Youtube
IMB
Updated on September 18, 2022Comments
-
IMB over 1 year
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 has127.0.0.1
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
192.168.0.2
then the vbox is192.168.0.3
but now the vboxes is both127.0.0.1
) I am usingBridged Adapter
BTW.EDIT: 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.