The ReconfigVM method does not care if the new MAC address is a valid VMware MAC address. It does not even seem to care if the new MAC address string is a valid hex MAC address. So, use with care - one would not want to break networking on their precious VM by setting its NIC to have an invalid MAC address, or a duplicate, etc. What I need to know is what range of MAC addresses can I use without fear that one day some device may be connected to our network with that MAC? I have read the Wikipedia article on MAC addresses and this section seems to indicate that if I create an address with the form 02-XX-XX-XX-XX-XX then it is considered a locally administered address.
Features | Documentation | Knowledge Base | Discussion ForumsMaintaining and Changing the MAC Address of a Virtual Machine
When a virtual machine is powered on, VMware Workstation automatically assigns each of its virtual network adapters an Ethernet MAC address. MAC stands for media access control. A MAC address is the unique address assigned to each Ethernet network device.
The software guarantees that virtual machines are assigned unique MAC addresses within a given host system. In most cases, the virtual machine is assigned the same MAC address every time it is powered on, so long as the virtual machine is not moved (the path and filename for the virtual machine's configuration file must remain the same) and no changes are made to certain settings in the configuration file.
In addition, VMware Workstation does its best, but cannot guarantee, to automatically assign unique MAC addresses for virtual machines running on multiple host systems.
Avoiding MAC Changes
To avoid changes in the MAC address automatically assigned to a virtual machine, you must not move the virtual machine's configuration file. Moving it to a different host computer or even moving it to a different location on the same host computer changes the MAC address.
You also need to be sure not to change certain settings in the virtual machine's configuration files. If you never edit the configuration file by hand and do not remove the virtual Ethernet adapter, these settings remain untouched. If you do edit the configuration file by hand, be sure not to remove or change the following options:
ethernet[n].generatedAddress
ethernet[n].addressType
ethernet[n].generatedAddressOffset
uuid.location
uuid.bios
ethernet[n].present
In these options, [n] is the number of the virtual Ethernet adapter, for example ethernet0.
Note: To preserve a virtual Ethernet adapter's MAC address, you also must be careful not to remove the adapter. If you remove the adapter, then recreate it, the adapter may receive a different MAC address.
Manually Assigning a MAC Address
If you want to guarantee that the same MAC address is assigned to a given virtual machine every time, even if the virtual machine is moved, or if you want to guarantee a unique MAC address for each virtual machine within a networked environment, you can assign the address manually instead of allowing VMware Workstation to assign it automatically.
To assign the same, unique MAC address to any virtual machine manually, use a text editor to remove three lines from the configuration file and add one line. The configuration file has a.vmx extension at the end of the filename. On a Linux host, a virtual machine created with an earlier VMware product may have a configuration file with a .cfg extension.
Remove the three lines that begin with the following from the configuration file:
ethernet[n].generatedAddress
ethernet[n].addressType
ethernet[n].generatedAddressOffset
In these options, [n] is the number of the virtual Ethernet adapter — for example ethernet0.
Add the following line to the configuration file:
ethernet[n].address = 00:50:56:XX:YY:ZZ
In this line, XX must be a valid hexadecimal number between 00h and 3Fh, and YY and ZZ must be valid hexadecimal numbers between 00h and FFh. Because VMware Workstation virtual machines do not support arbitrary MAC addresses, you must use the above format.
So long as you choose a value for XX:YY:ZZ that is unique among your hard-coded addresses (where XX is a valid hexadecimal number between 00h and 3Fh, and YY and ZZ are valid hexadecimal numbers between 00h and FFh), conflicts between the automatically assigned MAC addresses and the manually assigned addresses should never occur.
Manual MAC address for a VMware guest
Vmware Manual Mac Range Reviews
If you’ve ever tried to manually specify a MAC address for a VMware ESX virtual machine, you might have encountered the error message:
The MAC address entered is not in the valid range. Valid values are between 00:50:56:00:00:00 and 00:50:56:3f:ff:ff.
Vmware Manual Mac Range Manual
The reasons why VMware force manual MAC addresses into this scope are unclear to me (probably to prevent collisions), but regardless, it can be an issue. I needed to specify a particular MAC address in the 00:04 range. The reason being we were retiring an old physical server running the FLEXlm licensing service and the licenses were granted for the MAC address of the NIC on that machine. Renewing the licenses for the new virtual machine turned out to be ridiculously expensive so our only real option was to “spoof” the MAC address.
Vmware Manual Mac Range 2
I then ran into the aforementioned issue. However, the problem was easily solved by setting the MAC address from within the guest operating system instead. In this case, the server was running Windows Server 2003 and changing the MAC address was as simple as modifying the parameter “networkaddress” in the properties for the NIC in device manager. Voila!