Solved

Cannot start VM on VMware ESXi 4.0.0 - get error 'there are insufficient licenses to complete this operation. feature vsmp not licensed, requires 8 have 4'

Posted on 2011-02-13
13
3,274 Views
Last Modified: 2013-11-11
We have an HP Proliant ML370 with 2 physical CPUs and 4 cores in each
We have installed VMware ESXi 4.0.0 on to it and have one VM installed.
We registered for the free ESXi license and have added this to the server and it shows up.
I have recently shut down the VM but cannot now start it again and am getting the error - 'there are insufficient licenses to complete this operation. feature vsmp not licensed, requires 8 have 4'

I thought with the free license that we could use the 2 physical CPUs with 4 cores in each. I am not totally sure what the VSMP is although now i notice that in the license details it mentions only 4-way Virtual SMP but clearly states 2 CPUs with 1-6 cores in each.

What are we doing wrong?

Product: ESXi 4 Single Server Licensed for 2 physical CPUs (1-6 cores per CPU)
License Key: xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Expires: Never

Product Features:
Up to 256 GB of memory
Up to 4-way virtual SMP

p.s. using vSphere client 4.0.0
0
Comment
Question by:IT4BusinessUK
  • 7
  • 2
  • 2
  • +2
13 Comments
 
LVL 117
ID: 34883634
how many CPU have you assigned to nthe virtual machine?
0
 
LVL 3

Expert Comment

by:andreibutu
ID: 34883635
Read here:http://www.vmware.com/products/vsphere/buy/editions_comparison.html
All versions support VMs with 4 way vSMP except for Enterprise Plus which gives 8 way vSMP
0
 
LVL 28

Accepted Solution

by:
bgoering earned 300 total points
ID: 34883641
Reconfigure (edit settings) on your virtual machine and change the number of processors from 8 to 4, then it should start right up.
0
 
LVL 28

Expert Comment

by:bgoering
ID: 34883650
You can use 2 physical processors with up to 6 cores each with your free license. However for any single vm to have more than 4 processors requires a higher (not free) license for ESXi
0
 
LVL 7

Assisted Solution

by:Cuteadder
Cuteadder earned 200 total points
ID: 34883652
that error message is saying that the VM is set to use eight cores, whilst your ESX server only has a license for four cores per VM...

you need to go into the VM settings and change the cores to four...

then it should work fine...
0
 
LVL 28

Expert Comment

by:bgoering
ID: 34883656
The reason it ran with 8 before is that while in "trial" mode, all of the features including 8-way vsmp are available to you. Go to the configuration tab in vSphere client and select Licensed Features and it will tell you what all you can do with the free license.
0
Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

 
LVL 7

Expert Comment

by:Cuteadder
ID: 34883670
bgoering is onto something there, but you still need to change the number of core's in the settings... you don't have the right license to run it any other way...

best practice is only one core per server anyway... this seperates everything...
0
 

Author Comment

by:IT4BusinessUK
ID: 34883710
Changing to 4 CPUs and 8GB RAM does allow it to start up. I understand now about the licensing and the limit on cores per VM. I am worried that the SBS2008 will not perform as well now?

Also it will not start with the 12GB RAM as was originally. Does not start with 10GB either. Will start with 8GB. Again can someone possibly explain why this is and if I should take action to sort this or if 8GB is going to be OK.

Since the Enterprise Plus license is pretty expensive we would consider the Standard license or the Small Business license and I assume these don't allow cores per VM? Is it more of a big business requirement?

What are the limits for RAM per VM? is 8 the max under the free license?

Thanks for comments so far - all really helpful!
0
 
LVL 28

Expert Comment

by:bgoering
ID: 34883712
@cuteadder - as I said in my first response...
0
 
LVL 28

Expert Comment

by:bgoering
ID: 34883735
I am not aware that the free license limits the memory size for guests. It does limit the host to 256 GB. In edit settings check the Guest OS type is set to Windows 2008.

Enterprise plus is the only edition that allows 8-way vsmp.
0
 
LVL 117
ID: 34883739
Are you sure you need 4 CPUs and 12GB of ram in the SBS server?
0
 
LVL 28

Expert Comment

by:bgoering
ID: 34883742
I would venture to guess that 8GB woulld be plenty for SBS... Doesn't that limit you to a certain number of clients.

I would probably drop back to 1 vcpu and 4GB of memory and observe the guest. If you see lots of page faulting up the RAM. If you see sustained periods of high CPU add another procesor - it is very easy to do.
0
 
LVL 28

Expert Comment

by:bgoering
ID: 34883766
Do you plan on putting more vms on the box? If you do then resource management becomes a bit more important. I can understand you wanting to give all of the resources of the physcal box to a vm, but it isn't generally done.

On the 8GB limit, it is possible the datastore where the vm is stored is running out of space. This can happen easily if you have snapshots. How it is relevent is that a VM can't start if there isn't enough free space on the datastore (or wherever swapfile is configured to be placed) to create a swap file equal in size to configured memory.

How much free space is there?
0

Featured Post

Free book by J.Peter Bruzzese, Microsoft MVP

Are you using Office 365? Trying to set up email signatures but you’re struggling with transport rules and connectors? Let renowned Microsoft MVP J.Peter Bruzzese show you how in this exclusive e-book on Office 365 email signatures. Better yet, it’s free!

Join & Write a Comment

Create your own, high-performance VM backup appliance by installing NAKIVO Backup & Replication directly onto a Synology NAS!
This is an issue that we can get adding / removing permissions in the vCSA 6.0. We can also have issues searching for users / groups in the AD (using your identify sources). This is how one of the ways to handle this issues and fix it.
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now