admin
Immortal
Immortal

VMX Extras

Another mini program - this one makes it easier to edit vmx files by providing a GUI for some common options:

\* BIOS delay

\* Show/hide prompts

\* Paravirtualization

\* VNC server

\* Absolute/relative mouse

\* Loop/power down on CLIHLT

\* Buffered I/O

\* USB Debugging

\* USB HID

0 Kudos
20 Replies
DaveP
Commander
Commander

Brilliant! I just started doing something similar. Is there any chance this could be an open source project?

0 Kudos
saxa
Expert
Expert

Eric,

the Workstation and Server users would also like to see this product; running on Windows and Linux.

So the opensource idea is not as bad Smiley Wink

0 Kudos
DaveP
Commander
Commander

0 Kudos
RDPetruska
Leadership
Leadership

Saxa,

I've already got the VMX Builder which allows you to edit all (or at least most) of this stuff. And I have reports of Linux users getting it to work as well via WINE. Smiley Happy

Any requests for additional parameters, send email to my support address. And remember that some of these parameters Eric is setting are currently Fusion-only. I keep up very well with the betas/RCs of Server, Player, and Workstation - adding new parameters, etc. basically as soon as they are available. I had to scramble during Wks6 RC2 build, as they changed a few of the parameters and GUI locations! Smiley Happy

0 Kudos
walterwatts
Enthusiast
Enthusiast

This is much appreciated etung.

However, pardon my hesitance in dl'ing and opening the .zip on my iMac without knowing what will happen.

(I'm fairly new to OS X and while I've installed quite a few programs and understand OS X's underpinnings more than most, I'm pretty conservative)

Will it (the VMX Extras attachment) automatically install as a menu item in Fusion or do I need to do something else?

Thanks in advance,

Walter

0 Kudos
admin
Immortal
Immortal

There is no installation - since it's a simple program, it'll run from anywhere you put it. It is also standalone and does not affect Fusion, you can even use it without Fusion installed. Uninstallation is also simple, just delete the unzipped file.

What the program does is parses a file ending in ".vmx" and, if you tell it to, inserts one of several preconfigured strings. You can also use it to add arbitrary settings. It's just stuff you can do yourself with a text editor, but it's here for people who don't feel comfortable doing that.

0 Kudos
Yaztromo
Enthusiast
Enthusiast

Any consideration for making this and your vdiskManager GUI open source? There are a wide variety of additions and refinements I'd be willing to contribute to the code if it was available for easy modification online.

Yaz.

0 Kudos
todivefor
Enthusiast
Enthusiast

I just downloaded VMX Extras. When I try to execute it, it does nothing. It loads in the dock, but does not open a dialogue box. I must be doing something wrong. Running Fusion 1.1 (62573).

Macbook Pro 2012, 16GB, Samsung EVO 850 - !TB HD Mac OS X 10.12.6 Windows 10 Ububtu 14.04 LTS
0 Kudos
admin
Immortal
Immortal

The UI is unpolished, and is something I'll improve in my Copious Spare Time*, you have to tell it to open the file you want to edit. In OS X, the active program is bolded in the upper left menu - when you open VMX Extras, it should become the active application (even though it doesn't have a window).

  • - and once my hard drive gets recovered. Have you backed up today? I didn't! Oops...

0 Kudos
todivefor
Enthusiast
Enthusiast

Never mind. Another dumb user error. Just had to file|open VMX file.

Macbook Pro 2012, 16GB, Samsung EVO 850 - !TB HD Mac OS X 10.12.6 Windows 10 Ububtu 14.04 LTS
0 Kudos
todivefor
Enthusiast
Enthusiast

etung,

You beat by about a minute. I bought Fusion after trialing it and Parallels. The main reason was support like this.

Thank you.

Macbook Pro 2012, 16GB, Samsung EVO 850 - !TB HD Mac OS X 10.12.6 Windows 10 Ububtu 14.04 LTS
0 Kudos
hollistonma
Enthusiast
Enthusiast

I have the same problem with a URC remote control (MX-900). I am running Windows XP on a MacBook Pro using Fusion (version 1.1.3 94249). I do not use Boot Camp. The Mac (by itself) recognizes the URC when connected to the USB port but when XP does not. I see the solution above but I cannot locate the vmx file. When I use spotlight to find the file (using ".vmx" as the search term), spotlight does not find any files. What am I doing wrong and how can I find the vmx file? Any help would be greatly appreciated. Thanks.

0 Kudos
WoodyZ
Immortal
Immortal

Have a look at the Virtual Machine Files section in .

0 Kudos
hollistonma
Enthusiast
Enthusiast

Woody,

Thanks. Made the adjustment to the confiuration file and XP now recognizes the remote control. Remote is now programmed!

0 Kudos
BoyceMACme
Contributor
Contributor

I have downloaded your nice VMX Extras and opened the vmx file. However, I am pretty new to VMX config file format so I have no idea how exactly I should to do add additional Ethernet interface on my MacBook Pro.

On my MacBook Pro, there is Airport wireless LAN, onboard Ethernet port and USB-Ethernet port, where I bought the Apple manufactured USB-Ethernet interface. Here below is the output of ifconfig:

BMBP:tokamak200 boyce$ ifconfig

lo0: flags=8049 mtu 1500

inet 172.16.1.1 netmask 0xffffff00 broadcast 172.16.1.255

ether 00:50:56:c0:00:01

Based on above ifconfig, would you mind suggesting me what I have to add by using of VMX Extra? I also attached VMX config as your reference.

0 Kudos
WoodyZ
Immortal
Immortal

I have downloaded your nice VMX Extras and opened the vmx file. However, I am pretty new to VMX config file format so I have no idea how exactly I should to do add additional Ethernet interface on my MacBook Pro.

Have a look at: VMware Fusion (menu bar) > Help > VMware Fusion Help > Managing Virtual Machines > Configuring the Network Connection > Adding a Network Adapter

In other words add the network adapter first and then either manually edit the .vmx file or use VMX Extras to modify accordingly based on Tokamak directions.

0 Kudos
BoyceMACme
Contributor
Contributor

Exactly speaking, I would like to create vmnet2 and vmnet3 and bridge them to en1 and en2. Now vmnet0 has been bridged to en0. By using tokamak script, it can allow me to modify vmnet1 and vmnet8 ip address, but I cannot find any option guiding me to create vmnet2 and vmnet3 and bridge them to en1 and en2 physical interface.

By following the "VMware Fusion (menu bar) > Help > VMware Fusion Help > Managing Virtual Machines > Configuring the Network Connection > Adding a Network Adapter", I have created two additional Network Adapter and I can also see two network-interface in VMWare XP. However, they were all bridged to en0. In VMX file, I can see below ethernet:

ethernet0.addressType = "generated"

ethernet0.connectionType = "bridged"

ethernet0.generatedAddress = "00:0c:29:e8:cf:19"

ethernet0.generatedAddressOffset = "0"

ethernet0.linkStatePropagation.enable = "TRUE"

ethernet0.pciSlotNumber = "33"

ethernet0.present = "TRUE"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet1.addressType = "generated"

ethernet1.connectionType = "bridged"

ethernet1.generatedAddress = "00:0c:29:e8:cf:23"

ethernet1.generatedAddressOffset = "10"

ethernet1.linkStatePropagation.enable = "TRUE"

ethernet1.pciSlotNumber = "37"

ethernet1.present = "TRUE"

ethernet1.wakeOnPcktRcv = "FALSE"

ethernet2.addressType = "generated"

ethernet2.connectionType = "bridged"

ethernet2.generatedAddress = "00:0c:29:e8:cf:2d"

ethernet2.generatedAddressOffset = "20"

ethernet2.linkStatePropagation.enable = "TRUE"

ethernet2.pciSlotNumber = "38"

ethernet2.present = "TRUE"

ethernet2.wakeOnPcktRcv = "FALSE"

I do not have to modify vmnet1 and vmnet8 ip address, but I need to bridge en1 and en2 to additional vmnet. So, here below are the two tasks I would like to accomplish:

1. How to create two additional vmnet?

2. How to bridge the created vmnet to en1 and en2? FYI.... en0 = onboard ethernet port, en1 = Airport wireless, en2 = USB-Ethernet

Sorry for too many request.

0 Kudos
WoodyZ
Immortal
Immortal

1. How to create two additional vmnet?

2. How to bridge the created vmnet to en1 and en2? FYI.... en0 = onboard ethernet port, en1 = Airport wireless, en2 = USB-Ethernet

Read as it shows how to do it!

0 Kudos
BoyceMACme
Contributor
Contributor

After a lot of study of "VM@Work Tokamak.pdf" and trial, I discovered that I have to use "wizard" when I execute "sudo ./tokamak.sh --modify", which is something not documented, to add additional vmnet. Here below is the terminal output:

BMBP:tokamak200 boyce$ sudo ./tokamak.sh --modify

Password:

You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are?

(yes/no) n

Do you want networking for your virtual machines? (yes/no/help) y

Would you prefer to modify your existing networking configuration using the

wizard or the editor? (wizard/editor/help) w

The following bridged networks have been defined:

. vmnet0 is bridged to en0

Do you wish to configure another bridged network? (yes/no) y

Configuring a bridged network for vmnet2.

Your computer has multiple ethernet network interfaces available: en2, en1.

Which one do you want to bridge to vmnet2? en1

The following bridged networks have been defined:

. vmnet0 is bridged to en0

. vmnet2 is bridged to en1

Do you wish to configure another bridged network? (yes/no) y

Configuring a bridged network for vmnet3.

The following bridged networks have been defined:

. vmnet0 is bridged to en0

. vmnet2 is bridged to en1

. vmnet3 is bridged to en2

All your ethernet interfaces are already bridged.

Do you want to be able to use NAT networking in your virtual machines? (yes/no)

n

Removing a NAT network for vmnet8.

This program previously created the directory /Library/Application

Support/VMware Fusion/vmnet8/, and was about to remove it. Since there are files

in that directory that this program did not create, it will not be removed.

Do you want to be able to use host-only networking in your virtual machines?

n

Removing a host-only network for vmnet1.

VM@Work Tokamak 2.0.0: Display settings

The following virtual networks have been defined:

. vmnet0 is bridged to en0

. vmnet2 is bridged to en1

. vmnet3 is bridged to en2

VM@Work Tokamak 2.0.0: Extended network scripting - Dave Parsons

Bridged networking on vmnet0 using en0 is running

Bridged networking on vmnet2 using en1 is running

Bridged networking on vmnet3 using en2 is running

However, as Dave has ever mentioned that it is not good to delete vmnet1 and vmnet8, so I run "sudo ./tokamak.sh --install" again.

BMBP:tokamak200 boyce$ sudo ./tokamak.sh --install

VM@Work Tokamak 2.0.0: Installer started

VM@Work Tokamak 2.0.0: Stop daemons and kexts

VM@Work Tokamak 2.0.0: Create backup folders

VM@Work Tokamak 2.0.0: Save original files

VM@Work Tokamak 2.0.0: Set boot script

You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are?

(yes/no)

Do you want networking for your virtual machines? (yes/no/help)

Would you prefer to modify your existing networking configuration using the

wizard or the editor? (wizard/editor/help)

The following bridged networks have been defined:

. vmnet0 is bridged to en0

. vmnet2 is bridged to en1

. vmnet3 is bridged to en2

All your ethernet interfaces are already bridged.

Do you want to be able to use NAT networking in your virtual machines? (yes/no)

Configuring a NAT network for vmnet8.

Do you want this program to probe for an unused private subnet? (yes/no/help)

'ping' -q -t 10 172.16.184.1 > /dev/null status = 2

The subnet 172.16.184.0/255.255.255.0 appears to be unused.

The following NAT networks have been defined:

. vmnet8 is a NAT network on private subnet 172.16.184.0.

Do you wish to configure another NAT network? (yes/no)

Do you want to be able to use host-only networking in your virtual machines?

Configuring a host-only network for vmnet1.

Do you want this program to probe for an unused private subnet? (yes/no/help)

'ping' -q -t 10 172.16.125.1 > /dev/null status = 2

The subnet 172.16.125.0/255.255.255.0 appears to be unused.

The following host-only networks have been defined:

. vmnet1 is a host-only network on private subnet 172.16.125.0.

Do you wish to configure another host-only network? (yes/no)

VM@Work Tokamak 2.0.0: Display settings

The following virtual networks have been defined:

. vmnet0 is bridged to en0

. vmnet1 is a host-only network on private subnet 172.16.125.0.

. vmnet2 is bridged to en1

. vmnet3 is bridged to en2

. vmnet8 is a NAT network on private subnet 172.16.184.0.

VM@Work Tokamak 2.0.0: Extended network scripting - Dave Parsons

Bridged networking on vmnet0 using en0 is running

Host-only/NAT networking on vmnet1 using 172.16.125.1/255.255.255.0 is running

DHCP server on vmnet1 is running

Bridged networking on vmnet2 using en1 is running

Bridged networking on vmnet3 using en2 is running

Host-only/NAT networking on vmnet8 using 172.16.184.1/255.255.255.0 is running

DHCP server on vmnet8 is running

NAT networking on vmnet8 is running

VM@Work Tokamak 2.0.0: Installer completed

BMBP:tokamak200 boyce$ ifconfig

lo0: flags=8049 mtu 1500

inet 172.16.125.1 netmask 0xffffff00 broadcast 172.16.125.255

ether 00:50:56:c0:00:01

After that, I started to use VMX Extras to modify the VMX file. Originally I did not pay attention that seting is the key point to map vmnet to any ethernet specified in VMX file. So, I was failed originally. After some trials, I found that when I set , VMware cannot recognize . Only when I set it back to "custom", then it works. Here below is ethernet portion of my working VMX by adding and mapping additional two ethernet interface.

ethernet0.addressType = "generated"

ethernet0.connectionType = "custom"

ethernet0.generatedAddress = "00:0c:29:e8:cf:19"

ethernet0.generatedAddressOffset = "0"

ethernet0.linkStatePropagation.enable = "TRUE"

ethernet0.pciSlotNumber = "33"

ethernet0.present = "TRUE"

ethernet0.vnet = "VMnet0"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet1.addressType = "generated"

ethernet1.connectionType = "custom"

ethernet1.generatedAddress = "00:0c:29:e8:cf:23"

ethernet1.generatedAddressOffset = "10"

ethernet1.pciSlotNumber = "37"

ethernet1.present = "TRUE"

ethernet1.vnet = "VMnet2"

ethernet2.addressType = "generated"

ethernet2.connectionType = "custom"

ethernet2.generatedAddress = "00:0c:29:e8:cf:2d"

ethernet2.generatedAddressOffset = "20"

ethernet2.pciSlotNumber = "38"

ethernet2.present = "TRUE"

ethernet2.vnet = "VMnet3"

FYI..... en0 = Onboard Ethernet port, en1 = Airport Wireless port, en2 = Apple USB-Ethernet port

So, now I can feel free to connect my MacBook Pro VMWare image to three different physical subnets.

0 Kudos