After clone the VM within Virtual box, I receive the error message “
Device eth0 does not seem to be present, delaying initialization.” when start the network service.
The /etc/sysconfigu/network-scripts/ifcfg-eth0 does exist. The issue is that the network device eth0 is non longer exist. The VM clone processes create the new device eth1.
The device file is at /sys/class/net.
ip link show
We can rename the device by using the up command.
ip link set eth1 name eth0
After the device being renamed, we can successfully bring up the network interface.
I tried to rename but 'RTNETLINK answers: Device or resource busy '
ReplyDeletehow can i fix?
Please help me
hi i THOUGHT i have same problem as you..
ReplyDeletebut when i saw the result of command, i got "Device "eth0" does not exist."
actually, i've tried to remove all of the files in a folder somewhere because of some blogs..
but after that, my network is totally broken.
now.. i'm eager to turn it back..
please, any advice will be appreciated.
thank you
Delete networking interface rules file so that it can be regenerated and reboot your CentOS system.
ReplyDelete# rm /etc/udev/rules.d/70-persistent-net.rules
# reboot
Try the below command it worked for me
ReplyDelete# ifdown eth0
# rm /etc/sysconfig/network-scripts/ifcfg-eth0
# rm /etc/udev/rules.d/70-persistent-net.rules
# reboot
thank you for replying.
ReplyDeletefortunately i've solved the problem somehow..
I can't be sure but as my memory, I might setup another CentOS machine and copied the network interface files
or.. I just typed "setup" and reset the configuration.
anyway, again, thank you for your replies you guys
This comment has been removed by the author.
ReplyDeleteHi,
ReplyDeleteIts solved my problem temporally. But the same thing is reoccurred once system reboot.
Please help me with permanent solution.
Regards,
Tarak Nath