- Advertisement -
HomeVirtualizationVMwareHow to Install VMware VCSA 6.7 with less than 10GB RAM

How to Install VMware VCSA 6.7 with less than 10GB RAM

What

Install VMware VCSA 6.7 with less than 10GB RAM

If you are building a home lab (with VMware Workstation), more often than not you’ll be struggling with the resources of your physical PC, in general with the amount of memory. New versions of vSphere require at least 10GB RAM for “Tiny” VCSA deployments. This also means that the (virtual) server hosting VCSA should have even more RAM, over 10GB, to reserve some for the hypervisor.

If you don’t have these minimum requirements, you’ll get a warning message as below.

not enough memory on host for the selected size

For a VMware Workstation lab, you’ll only create a few VMs to test and play around with, yet this minimum amount of RAM required seems to be too high, and probably you’ll need extra memory for other services and applications.

For my environment, I want to change the minimum hardware requirements from 10GB to 6GB, of a tiny deployment.

How

Note: The resources required for the different VCSA deployments are the recommendations by VMware. These recommendations guarantee that your vSphere environment will work in full harmony with all VMware products. DO NOT change these parameters in a production environment.

  1. From the VMware VCSA installation folder, go to Vcsa-ui-installer \ win32 \ resources \ app \ resources.
  2. Open the file named layout.json with Notepad. You might want to create a copy of this file first.
  3. Inside the layout.json file, scroll down to “tiny”. There are several options so make sure you select the one with the label: "Tiny vCenter Server with Embedded PSC", which is based on Deployment size, Tiny, Storage size, default (300GB), and with Embedded PSC.
Install VMware VCSA 6.7 with less than 10GB RAM
  1. Change “memory” to the desired value. 6GB (6144MB) in my case. Save the changes.
  2. Next time you run VCSA installation you’ll see that the Tiny deployment has been down-seized to 6GB (or your value)
not enough memory on host for the selected size
  1. Now you can continue with the deployment of your VCSA.
- Advertisement -

Note: This change won’t be reflected on the Virtual Hardware when the VCSA (VM) is created, it can’t be changed and you still see 10GB. But from the Resource Monitor, you’ll see that 6GB is used as a limit.

Juan Mulford
Juan Mulford
I have been active in IT for over fourteen years now. I am a solutions architect, working with storage, virtualization, and VDI solutions. For the past ten years, I have been living and working in Taiwan.

8 COMMENTS

    • Hi Ryan, be sure you have admin permissions at the location you want to save the file. Or try copying the ISO files into a different folder. This shouldn't be a VMware issue.

  1. open it in poweriso , copy file into your pc , modify your file, save it ; and replace it into iso ; save iso

  2. I tried this recently and it ended up using 10Gb memory 😦
    I thought it was the answer to all my prayers

Leave a Reply

- Advertisement -

Popular Articles

mulcas.com-Raspberry-Pi

Raspberry Pi OS in a Virtual Machine with VMware

4
Although the Raspberry Pi OS is designed and optimized for the Raspberry Pi module, it is possible to test and use it without its hardware, with VMware. This solution can be useful if you are a developer (or just a curious guy) and don't have a Raspberry Pi module with you
Unable to delete inaccessible datastore

Unable to delete an "inaccessible" datastore

4
I was switching my storage array, so I migrated the VMs from that old datastore/storage to a new datastore/storage. The old datastore was shared by 3 ESXi hosts, no cluster. After migrating the VMs and unmount/delete the datastore, it was still presented in two of the ESXi hosts and was marked as inaccessible.
mulcas.com-VMware-OVF-Tool

How to export a Virtual Machine using the VMware OVF Tool

8
The VMware OVF Tool is implemented by VMware for easily importing and exporting virtual machines in Open Virtualization Format (OVF) standard format. Here, I want to show you how to download and install it, and then how to use it from a Windows machine.
This is not a valid source path / URL

This is not a valid source path / URL - SourceTree and Gitlab

0
I have been working on a project with a friend who set up a repository in Gitlab but even though I was able to view all projects on it, I couldn’t really join the repository. I was using SourceTree and Gitlab.
Couldn't load private key - Putty key format too new

Couldn't load private key - Putty key format too new

3
couldn't load private key - Putty key format too new.” This issue happens when you use PuTTygen to generate or convert to a ppk key. Here is how to fix it. 
- Advertisement -

Recent Comments