nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issues cloning Linux VMs

JockVSJock

Was wondering if others we having this issues.

Where I work we run a number of various RHEL 5/6 and they are either 32 or 64 bit machines.

From VC, we use Converter to move from our virtual prod environment to our dev environment. In this case, we have a bunch of updates, we want to run first in dev and once they prove successful, we will do it again in prod.

Once we successfully clone and then move into our dev environment, this is where the issues start.

We have issues with MAC addresses, which I have to manually change to match the MAC address that VMWare has assigned and then I get a range of networking issues.

I've googled around and see that others have the issue as well and really didn't see a solid solution and was wondering what others had seen and did to try and fix.

thanks

Find more posts tagged with

SAVE $250 on Your Boot Camp — Use Code "EXAM26"

Exclusively for TechExams members for Infosec Boot Camps starting before April 30, 2026

View Boot Camps

Comments

Essendon

Why don't you use snapshots?

JockVSJock

Does that create a VM without all of the issue?

Essendon

Doesn't create a VM per se, but let's you test your updates and if you like them you commit the snapshot. If you don't like the results, you just roll back to point where the snapshot was taken. What's running in these VMs?

JockVSJock

Gonna run that by the VMWare admin and see what he thinks.

thanks

Pupil

This is a frequent problem I face when cloning RHEL/CentOS 6 VMs. What I do is first delete the file /etc/udev/rules.d/70-persistent-net.rules and then remove the line with the MAC address in /etc/sysconfig/network-scripts/ethX where X is the NIC # (starts at 0). Then restart network services with service network restart.

Cable_guy

Agreed with above.

Clear the persistent rules file and that should fix your issue. I've seen this issue rear its head on many distros and VMware.

cs8400

Pupil wrote: »

This is a frequent problem I face when cloning RHEL/CentOS 6 VMs. What I do is first delete the file /etc/udev/rules.d/70-persistent-net.rules and then remove the line with the MAC address in /etc/sysconfig/network-scripts/ethX where X is the NIC # (starts at 0). Then restart network services with service network restart.

Thanks! I too have run into this issue before. Good to know.