VMware Cloud Community
leecassidy
Contributor
Contributor
Jump to solution

Problem cloning JeOS 8.04 on ESXi

Hi

I have an ESXi server running well and have built a number of VMs using JeOS 8.04, I have started to use VM Explorer from Trilead which is a very cost effective way to manage multiple ESXi servers.

I now want to be able to clone built VMs and use them to create multiple copies of our application environment, VMX allows me to create and register a clone but when started up even though a new UID has been created for the VM it will not start up networking, checking the settings it has a different mac address after the UID create.

What a I missing?

Reply
0 Kudos
1 Solution

Accepted Solutions
cody_bunch
Hot Shot
Hot Shot
Jump to solution

Different MAC address is the expected behavior. You don't want duplicate MAC addresses. The problem is, with ubuntu (JeOS) it picks up the new MAC as being a new NIC.

You'll likely want to do something similar to:

sudo vim /etc/udev/rules.d/70-persistent-net.rules

and remove the eth0 entry before the clone, or clean it up afterwards.

-Cody Bunch

vExpert, VCP VI3

-Cody Bunch http://professionalvmware.com

View solution in original post

Reply
0 Kudos
4 Replies
jbruelasdgo
Virtuoso
Virtuoso
Jump to solution

you are not missing something. the behavior about this is that as you are cloning (creating a copy), the mac address changes automatically, which by the way is normal. It does not matter if it is Windows, Linux, Solaris, etc.

the only way to keep the mac address is to set it manual

regards

Jose

Jose B Ruelas http://aservir.wordpress.com
cody_bunch
Hot Shot
Hot Shot
Jump to solution

Different MAC address is the expected behavior. You don't want duplicate MAC addresses. The problem is, with ubuntu (JeOS) it picks up the new MAC as being a new NIC.

You'll likely want to do something similar to:

sudo vim /etc/udev/rules.d/70-persistent-net.rules

and remove the eth0 entry before the clone, or clean it up afterwards.

-Cody Bunch

vExpert, VCP VI3

-Cody Bunch http://professionalvmware.com
Reply
0 Kudos
leecassidy
Contributor
Contributor
Jump to solution

This was the issue, JeOS was caching the mac address of the donour VM the easy way was just to delete /etc/udev/rules.d/70-persistent-net.rules and reboot this worked fine thank you for your help.

Reply
0 Kudos
cody_bunch
Hot Shot
Hot Shot
Jump to solution

Another method of doing this, is to edit the ‘persistent-net-generator.rules’ file to include something similar to:

# ignore VMware virtual interfaces
ATTR{address}=="00:0c:29:*", GOTO="persistent_net_generator_end"

That ought to fix it on an ongoing basis.

-Cody Bunch

vExpert, VCP VI3

-Cody Bunch http://professionalvmware.com
Reply
0 Kudos