After cloning VM in vSphere, network.service fails to start
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After cloning VM in vSphere, network.service fails to start
Hi LQ community! After I cloned a production RHEL 7.6 server in VMware vSphere 6.5 to a sandbox, the network.service fails to start.
I'm using VMware vSphere Client version 6.5.0.23000 to clone a RHEL VM. I've tried manually starting the networking service after it fails to come up during boot and receive the prompt: 'See "systemctl status network.service" and "journalctl -xe" for details.'
journalctl -xe shows:
network.service: control process exited, code=exited status=1
Failed to start LSB: Bring up/down networking.
Unit network.service has failed.
Unit network.service has begun starting up.
bringing up loopback interface: [ OK ]
Bringing up interface eth0: RTNETLINK answers: File exists
[ OK ]
Bringing up interface p1p1: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device p1p1 does not seem to be present, delaying initialization.
I've been Google searching for quite a while on this and saw a lot of similar *but* different instances of this error, so I tried adding the MAC address to the ifcfg-eth0 file and restarted the network. Still failed. Ideas / tips are appreciated.
My guess is udev has a persistence rule for the NICs, and since your NICs are now "different", they have different names. Try this:
Code:
cd /etc/sysconfig/network-scripts
ip link list
ls
If the interfaces shown by IP differ from the files in network-scripts, rename them to match. Make sure you edit them. You will probably have to comment out or update UUID as well as the NAME and DEV lines. I don't have an RHEL box available at the moment to check, but NAME and DEV might be a little different.
This is due to MAC address of the nic.
As the MAC Address is changing on your clone, on clone you should edit the /etc/sysconfig/network-scripts/ifcfg-ensXXX and remove the MAC address of that correspond to the original VM. You do not need to add the new one.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.