When restarting the network service on a Linux virtual machine, you may encounter the following error:<\/p>\n\n\n\n
\nDevice eth0 does not seem to be present, delaying initialization<\/p>\n<\/blockquote>\n\n\n\n
This issue commonly occurs when the MAC address configured in the network configuration file does not match the MAC address of the current virtual network adapter. It can also occur when the network adapter of the virtual machine has been changed or recreated.<\/p>\n\n\n\n
In this article, we will explain how to resolve the \u201cDevice eth0 does not seem to be present\u201d<\/strong> error.<\/p>\n\n\n\n
Prerequisites<\/h2>\n\n\n\n
Before proceeding, make sure you have:<\/p>\n\n\n\n
\n
- Root or sudo access to the Linux server.<\/li>\n\n\n\n
- Console or SSH access to the virtual machine.<\/li>\n\n\n\n
- A backup of the network configuration files before making changes.<\/li>\n<\/ol>\n\n\n\n
Implementation<\/h2>\n\n\n\n
Step 1: Remove the Persistent Network Rules File<\/h3>\n\n\n\n
Remove the existing persistent network rules file using the following command:<\/p>\n\n\n\n
rm \/etc\/udev\/rules.d\/70-persistent-net.rules<\/pre>\n\n\n\nThis file may contain the MAC address information of the previously configured network adapter.<\/p>\n\n\n\n
Step 2: Update the Network Configuration<\/h3>\n\n\n\n
Open the
eth0<\/code> network configuration file:<\/p>\n\n\n\nvi \/etc\/sysconfig\/network-scripts\/ifcfg-eth0<\/pre>\n\n\n\nRemove the following entries from the configuration file if they are present:<\/p>\n\n\n\n
HWADDR=
UUID=<\/pre>\n\n\n\nSave and exit the file.<\/p>\n\n\n\n
Removing the old MAC address and UUID allows the operating system to detect and configure the current network adapter correctly.<\/p>\n\n\n\n
Step 3: Reboot the Server<\/h3>\n\n\n\n
Reboot the virtual machine:<\/p>\n\n\n\n
reboot<\/pre>\n\n\n\nAfter the server restarts, the network interface should be detected and configured automatically.<\/p>\n\n\n\n
Step 4: Verify the Network Interface<\/h3>\n\n\n\n
After the server comes back online, verify that the
eth0<\/code> interface is available:<\/p>\n\n\n\nifconfig eth0<\/pre>\n\n\n\nAlternatively, use:<\/p>\n\n\n\n
ip addr show eth0<\/pre>\n\n\n\nYou can also verify the network service status:<\/p>\n\n\n\n
service network status<\/pre>\n\n\n\nConclusion<\/h2>\n\n\n\n
The \u201cDevice eth0 does not seem to be present, delaying initialization\u201d<\/strong> error is commonly caused by a mismatch between the configured network adapter details and the actual virtual network adapter.<\/p>\n\n\n\n
Removing the old persistent network rules and clearing the outdated MAC address and UUID<\/strong> from the
ifcfg-eth0<\/code> configuration allows the operating system to detect the current network adapter correctly. After rebooting the server, the network interface should come up automatically.<\/p>\n\n\n\nFAQs<\/h2>\n\n\n\n
1. What causes the \u201cDevice eth0 does not seem to be present\u201d error?<\/h3>\n\n\n\n
The error is commonly caused by a mismatch between the MAC address configured in the network configuration and the MAC address of the current network adapter.<\/p>\n\n\n\n
2. When can this issue occur?<\/h3>\n\n\n\n
This issue can occur after changing, removing, or recreating a virtual network adapter on a virtual machine.<\/p>\n\n\n\n
3. Which file contains the persistent network adapter information?<\/h3>\n\n\n\n
On older Linux systems, the persistent network rules are stored in:<\/p>\n\n\n\n
\/etc\/udev\/rules.d\/70-persistent-net.rules<\/pre>\n\n\n\n4. Why should the HWADDR and UUID be removed?<\/h3>\n\n\n\n
If they belong to the previous network adapter, they can prevent the operating system from correctly identifying the current adapter.<\/p>\n\n\n\n
Talk to our experts<\/h2>\n\n\n\n