Good Morning,
Has anyone ran into a problem like this when installing vCenter Server 6 (embedded) on a physical machine (see screenshot)? The server has 8 GB of RAM installed so I'm not sure why VMWare's install process is being so picky about the exact detected memory. I did open a case with VMWare but I thought I'd check with the community as well to see if anyone has encountered this and has a quick solution. Thanks.
In some systems, some of the RAM is used as video memory. When this happens, the OS doesn't see exactly what is installed. If this is what's happening, you may need to add more memory in order to install vSphere 6.
Just came across this article that talks to your issue... Not much help though.
After talking with VMWare I found that if you run the embedded setup you need to add the memory requirements of the Platform Services Controller to the base requirements of vCenter server, meaning technically I need 10 GB of RAM on the server, if I'm reading it all correctly. VMWare does put a note in the requirements about it but I think they could improve upon their documentation and make the system requirement's table a bit more clear on this topic.
Anyway, I'm just going to take the easy way out and install more memory in the server and call it a day. Thanks for your help to those who replied.
Nate
Did anyone ever find a workaround for this? A test setup I have is limited to 1 module and the 16GB SO-DIMM modules are very expensive. Thanks.
When I talked with VMWare's tech support on this issue I was faced with 2 options, 1) Upgrade RAM or 2) Change the BIOS and/or OS settings so that the usable RAM went up to the required number that the VMWare installer requested. I chose to upgrade the RAM since it was a cost under $200 to do so, but I wasn't faced with having only a single memory slot. If you can't adjust the usable RAM to the OS then you'll have to increase physical RAM to my knowledge.
Seems a shame, there should be a bit more leeway on the 8GB limit. It's not a problem now, I made a virtual machine on a machine with more than 8GB RAM, and then cloned that onto a hard disk and put that into the server. Problem solved.
I got around this by running the install via cmd with the flag: SKIP_HARDWARE_CHECKS=1
I got around this by using the deploy ovf template option in vSphere fat client. Then pointing to the ova file located in vCSA iso.
Hi njtgcu
If you run the following command in Powershell this will stop the system check of the installation
Make sure you have the software locally on the Server.
Open PowerShell *would recommend to run as administrator
type in the following commands within PowerShell
to head to root directory
Enter the following command: Cd/
now navigate to the location of the Software
Enter the following command:cd\temp\Vsphere6.5\vCenter-Server
this will change depending on the location you stored your software
this will list all the files and directories within
Enter the following command: dir
Once you are in the correct location
enter the following command: .\VMware-vCenter-Server.exe "SKIP_HARDWARE_CHECKS=1"
*Remember to include capital letters when needed
Hope this helps!
I fixed it on 6.7, credit to this site:
https://blog.widmo.biz/homelab-vmware-vcenter-server-6-5-skip-hardware-ram-check/
vCenter 6.0 – run:
installer.exe "SKIP_HARDWARE_CHECKS=1"
vCenter 6.5 – edit file:
vcsa-ui-installer\win32\resources\app\resources\layout.json
set:
"tiny": { "cpu": 2, "memory": 4096, "host-count": 10, "vm-count": 100, "disk-swap": "25GB",
Aaaaaaa