Leadinggol

I wish to distribute a VMWare VM for users (who are technically challenged and unable to install a complex product). Users may run several instances of the VM in their environment, so it's essential that each VM have NIC's with unique MAC addresses.

Is there a way to distribute the VM in such a way that on first boot if forces new MAC addresses onto the NIC's?

Need asus p5s800-vm RAID CONTROLLER and MULTIMEDIA AUDIO CAST driver Here is the driver download page, there is a RAID driver for XP, and media controller: Driver Page. Please check with your supplier for exact offers. P5NE SLI Manual| Motherboards| ASUS USA. MyLogo3 Personalize your system with customizable boot logo The ASUS MyLogo 3 is the new feature present in the motherboard that allows you to personalize and add style to your system with customizable and animated boot logos.

If users just add the VM to their inventory and select 'moved' instead of 'copied' then they get the same MAC's (I believe).

I'm using VMWare WOrkstation 12 in case that matters.

1 Answer

The canonical 'correct' way to distribute VM images for VMware vSphere is to distribute .ova files created using ovftool, and then use the vSphere GUI to install the .ova file. This automatically distributes a 'copied' version of the virtual machine that has a different MAC address when deployed. However, there is a way to do the job if you're going to instead distribute a zipped up VMware Workstation directory. What you need to do is, immediately before you zip up the directory, is first copy the .vmx file someplace else. Then edit the vmx file and look for a line that looks like

Pss800 Vm Driver

Remove that line from the vmx file.

Then zip it up and distribute it. That should give you copy of the virtual machine that does not have a built in MAC address and that should generate a new MAC address upon deployment. (This is assuming a VM with a single Ethernet interface). Then copy the original .vmx file back into place.

Note that for certain operating systems, such as Red Hat Enterprise Linux 6, there are udev rules that tie a specific Ethernet interface to a specific MAC address. These must be removed to allow eth0 to come up after the deployment. If your operating system is one of those, that is a separate question.

Vmware Fusion 8 Download

Not the answer you're looking for? Browse other questions tagged vmware-esxivirtual-machinesnic or ask your own question.

Vmware Run Mac On Windows