Aloha -
This is where we are now -
8 Enterprise Licenses (4 hosts x 2 sockets)
3 hosts having 96gb RAM each - all of which are running at 28% RAM (4th host retired tomorrow due to host upgrades of the other 3)
Our VRAM entitlement is 8 x 32gb = 256gb
Currently used VRAM is 3 x (96 x .28) = 80.64gb
Is this correct??
Mahalo,
Bill
Singular confusion that seems to be somewhat common:
It is RAM *assigned* to *running* virtual machines. Not the used memory of the host.
While your used might be 28%, the assigned might be closer to 40%?
Bill -
The easiest way to find out your current vRAM levels is a tool like this one:
http://www.virtu-al.net/2011/07/14/vsphere-5-license-entitlements/
An "official" tool from VMware is coming soon. This one will work fine, but you have to start it with PowerCLI at the command line.
When attempting to run this I get an error "The Windows PowerShell snap-in 'VMware.Vim.Automatio,core' is not installed on this machine"
you need to be running the latest version of PowerCLI as well as PowerShell v2
If you have those installed you can try adding it from the PowerShell/PowerCLI prompt
>Add-PSSnapin VMware.VimAutomation.Core
As I posted in another thread, if you want to get the number without worrying about script errors just run the following cmdlet after connected to your vCenter server in PowerCLI (this works on 4.1 ESX/vCenter/PowerCLI, not sure if it errors on previous versions)
>Get-VM | Mesaure-Object -Property MemoryMB -Sum
It will return your total configured memory of all VM's in MB, divide by 1000 to convert to GB. Configured memory is what it looks for, not currently consumed.
If that number is lower than your license entitlement of 256gb then you're in the clear for the current configuration.
Thats my understanding as well, its the allocated memory to the running VMs that count towards the entitlement.
Pete Del Rey wrote:
Thats my understanding as well, its the allocated memory to the running VMs that count towards the entitlement.
Then your understanding is correct