DISCLAIMER: This ‘hack’ is UNSUPPORTED and should never be used in a Production Environment – for home labs though may be useful!
Whilst experiencing an issue with a corrupt SSO installation in vSphere 5.5, I discovered a reg hack that allowed me to continue to login to a vSphere environment with domain credentials until I could resolve the existing issue with SSO. This is a simple change and involves editing the vpxd.cfg file.
On the vCenter server navigate to vlxd.cfg file
For Windows 2003: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg
For Windows 2008: C:\ProgramData\VMware\\VMware VirtualCenter\vpxd.cfg
For the Appliance: /etc/vmware-vpx/
Open vpxd.cfg in a text editor
Search for the following:
Change ‘true’ to ‘false’ between the highlighted tags
Aside from my day job, buying a new house, studying for VCAP exams, presenting at VMUG’s (The Belgian VMUG is next week), I have a couple of personal side projects I’m working on, both virtualization related of course. The first exciting project is well under way and I hope to announce it very soon. They second is still in it’s infancy and is the reason for this blog post, so I’m hoping it works!
I’d like to reach out to all thin client vendors who offer thin clients with Teradici PCoIP chips built in to ‘donate’ or ‘loan’ a unit to me for some testing. You may be thinking, I work for a well known virtualization consultancy, surely I have some contacts I could call upon. Yes, I do, however I want to be completely upfront and honest this probably wont lead to a sale and is not in anyway associated with Xtravirt. You may also be thinking why don’t you just go and buy one for yourself. I could, but I’ve just bought a house, also buying a single unit wont get me any relationship with a vendor. Whilst I’m not intending to pester any vendor for information, perhaps some questions may come from my testing.
So why provide me with a unit? Well, I’ll certainly blog about your kindness, so please ping me a message on Twitter and let’s have a chat!
Whilst this is an imposed limit through the GUI, there is a workaround by amending the VMX file.
From Finder, navigate to your Virtual Machine files, Right Click the file for your Virtual Machine and select ‘Show Package Contents’.
From here all the virtual machine files will be displayed, search for the ‘VMX’ file, right click and select open with ‘Text Edit’
Amending the VMX file in Fusion, is the same as ESXi and Workstation. We need to search for the ‘mem size’ field and amend the value inside the quotation marks to our desired values. You will see form the images below, I’ve replaced 2GB with 16GB.
Save the change and close Text Edit and Finder and power on your virtual machine in VMware Fusion. You’ll notice when the VM is powered on, that a warning appears stating the machine is configured with an unsupported memory size
Tick the box to ignore the warning and wait for the machine to boot. Once booted you’ll notice your host has the desired amount of RAM….. easy.