ESXi doesn't lend itself to modification of the .vmx file

[roryg]

Hello,

I'm running an old 32-bit Suse Linux distro on a 64-Bit VM Workstation. I've modified the VMs vmx file with 'monitor_control.disable_longmode=1' in order to force the Guest OS to detect as 32 bit, otherwise a 32-bit application that needs to run on the guest Suse installation wont start properly.

That all works ok, but I need to do the same thing on our corporate ESXi server but have run into the followin problems:

1. Its possible, but not easy to modify the vmx file without ssh or ftp access. Am I missing something here?

2. Our local IT guy is reluctant to start hacking configuration files unless he's had some assurance that other VMs, or the whole server, wont be adversely affected by the change

I would be grateful if anyone could a) advise on the best way of modifying .vmx files on an ESXi server, and b) confirm that changing the vmx file on one guest VM wont interfere with anything else running on the host.

Thanks in advance,

RoryG

[DSTAVERT]

You can download the vmx file using the datastore browser. Edit the file with a text editor (NOT NOTEPAD) Notepad ++ works. and upload again. That setting shouldn't adversely affect other VMs but other ones possibly could (memory cpu)

[DSTAVERT · Accepted solution]

With the VM off you can add settings through the VI client.

Settings / Options / Advanced / General - Configuration parameters.

[lamw]

FYI - In ESX(i) 4.0, this has been made easier and can be done using the vSphere Client

If you want to automate this process, take a look at this script:

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at:

VMware Code Central - Scripts/Sample code for Developers and Administrators

VMware Developer Comuunity

Twitter: @lamw

If you find this information useful, please award points for "correct" or "helpful".

[roryg]

Thanks Folks, this has all be useful information. I was able to make the change from the client as per instructions (had to shut the machine down first of course - Doh!). Problem solved, works like a charm.

[DSTAVERT]

Glad we could help.