To get this new setting to stick, perform a full quit of VMware Fusion.app (⌘Q or right-click on the icon and click Quit). Important: You must allocate an IP address that is outside the range defined inside the DO NOT MODIFY SECTION section.
Important: My VM’s name is actually “Windows 8 圆4” so in the nf file you must refer to it with no spaces in the name, so Windows8圆4. On my system, this file is located in /Library/Preferences/VMware Fusion/vmnet8, so edit the file (use sudo): Copying the MAC address of my VM Step 2: Modify nf
Note: if the VM is powered on, the MAC address box will be greyed out. Then expand the “Advanced options” section at the bottom and copy the MAC address that you see there. Open the VM’s Settings and select “Network Adapter”. Step 1: Get your VM’s virtual MAC address So imagine my delight when I discovered that you can indeed allocate static IP addresses to VMs simply by editing a single config file. More recently, I’ve been testing out lot of different type 1 Hypervisors ( ESXi/vSphere, Proxmox, XenServer etc) which usually make the assumption that they will be given a static IP (which they should in the real world). Applications that I use that have references to those IP addresses always had to be reconfigured each time I wanted to use them. One thing that always bugged me is that Fusion allocated a different IP address to each VM every time it started up, or resumed from a suspend. I am an OSX user, and I run a lot of VMs using VMware Fusion 7 which I have been very happy with since I purchased it. Update: This technique also works in VMware Fusion 8!
0 kommentar(er)
