VMware

This Question is Answered

1 "helpful" answer available (6 pts)
4 Replies Last post: Mar 9, 2009 6:02 AM by cody.bunch  

Problem cloning JeOS 8.04 on ESXi posted: Mar 8, 2009 3:05 PM

Click to view leecassidy's profile Novice 4 posts since
Mar 8, 2009

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?

Re: Problem cloning JeOS 8.04 on ESXi

1. Mar 8, 2009 3:39 PM in response to: leecassidy
Click to view jbruelasdgo's profile Master vExpert 1,031 posts since
Dec 22, 2004

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

Re: Problem cloning JeOS 8.04 on ESXi

2. Mar 8, 2009 4:19 PM in response to: jbruelasdgo
Click to view cody.bunch's profile Hot Shot vExpert 194 posts since
Dec 28, 2007
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
http://professionalvmware.com

Re: Problem cloning JeOS 8.04 on ESXi

4. Mar 9, 2009 6:02 AM in response to: leecassidy
Click to view cody.bunch's profile Hot Shot vExpert 194 posts since
Dec 28, 2007
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
http://professionalvmware.com

VMware Beta Programs

Want to be Considered for Future Beta Programs?

Learn More

VMware Developer

Download SDKs, APIs, videos,
training, and more in the Developer community.

Learn More

Developer
Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld
Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

Only VMware ... Delivers Nexus 1000V

Ensure consistent, policy-based network capabilities to virtual machines across your data center.

Learn More

Communities