VMware Cloud Community
kgottleib
Enthusiast
Enthusiast
Jump to solution

Free ESXi details

could someone please shed light on where this currently stands.

1)  I realize that the new free ESXi 5.5 has lifted memory restrictions, but have these restrictions also been lifted for older versions?  Why would VMware remove the restriction to 5.5 but not earlier  versions?

2)  If the restriction is not lifted for 5.1, what is the actual  restriction?  is it 32GB of ram total in the server, or 32GB of ram per socket, I have seen it listed  both ways in various posts..

3)  if the restriction is not lifted for 5.1, what should a user expect to see should when they try to apply free license to 5.1 hypervisor that has more memory than X memory in the host? (I say X because I don't have question 2 answered  yet)

thanks.

Reply
0 Kudos
1 Solution

Accepted Solutions
kgottleib
Enthusiast
Enthusiast
Jump to solution

OK, thanks for your reply guys, you were mostly correct.  but I did feel the need to actually test this while waiting for reply, here's the final on this:

the host was built in eval mode the same way all hosts are built, it had 48GB of memory.  When I tried to add the free lic it first gave me an error stating that it didn't belong to the product.  this didn't make any sense.  I tried again and got the same error.. very frustrating.  One thing to note, I was connected direct to vmnic0 via my laptop on completely isolated network. 

I tried again, only the 3rd time I tried I was at my desk connecting to ESXi via vClient (I had internet access from this station), and this time the error message was completely different, it stated that I had too much memory, displayed the amount of memory (48GB), and stated that the lic would only support 32GB.

So the hypervisor does indeed start, but why wouldn't it, its still in eval mode.. and after eval mode is over, I believe ESXi will still boot to hypervisor, but you just can't power on any VMs.

So the tidbit about the hypervisor not starting or booting seems to be incorrect.

If anyone else would like to comment I will keep this post open for a few more days.

View solution in original post

Reply
0 Kudos
3 Replies
JarryG
Expert
Expert
Jump to solution

Ad.1) no, the older restriction remain in force

Ad.2) 32GB physical RAM for ESXi-server

Ad.3) on server with >32GB free ESXi (hypervisor) does not start

_____________________________________________ If you found my answer useful please do *not* mark it as "correct" or "helpful". It is hard to pretend being noob with all those points! 😉
abhilashhb
VMware Employee
VMware Employee
Jump to solution

kgottleib wrote:

1)  I realize that the new free ESXi 5.5 has lifted memory restrictions, but have these restrictions also been lifted for older versions?  Why would VMware remove the restriction to 5.5 but not earlier  versions?

This was a new change that happened in version 5.5 which will not be available for earlier versions.

2)  If the restriction is not lifted for 5.1, what is the actual  restriction?  is it 32GB of ram total in the server, or 32GB of ram per socket, I have seen it listed  both ways in various posts..

Actual restriction is 32GB as you mentioned. Its not Per Socket. Its on the whole.

3)  if the restriction is not lifted for 5.1, what should a user expect to see should when they try to apply free license to 5.1 hypervisor that has more memory than X memory in the host? (I say X because I don't have question 2 answered  yet)

It will no recognize anything more than 32GB. It will fail to boot.

Abhilash B
LinkedIn : https://www.linkedin.com/in/abhilashhb/

kgottleib
Enthusiast
Enthusiast
Jump to solution

OK, thanks for your reply guys, you were mostly correct.  but I did feel the need to actually test this while waiting for reply, here's the final on this:

the host was built in eval mode the same way all hosts are built, it had 48GB of memory.  When I tried to add the free lic it first gave me an error stating that it didn't belong to the product.  this didn't make any sense.  I tried again and got the same error.. very frustrating.  One thing to note, I was connected direct to vmnic0 via my laptop on completely isolated network. 

I tried again, only the 3rd time I tried I was at my desk connecting to ESXi via vClient (I had internet access from this station), and this time the error message was completely different, it stated that I had too much memory, displayed the amount of memory (48GB), and stated that the lic would only support 32GB.

So the hypervisor does indeed start, but why wouldn't it, its still in eval mode.. and after eval mode is over, I believe ESXi will still boot to hypervisor, but you just can't power on any VMs.

So the tidbit about the hypervisor not starting or booting seems to be incorrect.

If anyone else would like to comment I will keep this post open for a few more days.

Reply
0 Kudos