Folks,
We regularly see an issue with moving certain VM's into resource pools.
The message manifests as:
"The CPU resource shares for VMxxx are much lower than the virtual machine's in the resource pool. With its current share setting, the virtual machine will be entitled to 2% of the CPU resources in the pool. Are you sure you want to do this?"
Up until today I thought that either my DataCenter's VMware environment or perhaps my personal methods or techniques might have been at fault. That was the past...
Today, in VMware's classroom environment: "VMware Infrastructure3: install and Configure" This exact same problem happened to our \[classroom] environment as well. This was an environment of all cloned VM's, all guaranteed to have the same resource setup for all VM's. Just to be sure it wasn't a normal VM issue or a resource pool issue, we manually checked every one the VM's and the resource pool. Neither we students, nor the VCP certified instructor could find a viable reason for this warning message.
So, while I don't expect a resolution from the group, I am hoping to get through to the VMware folks monitoring these groups that a bug exists and needs addressing. Until then, does anyone have any thoughts?
I have the same issue and it is driving me insane. I have not put certain vms back into their pools with the concern that something was off here. Can anyone else confirm that this is a bug?
Matthew
Kaizen!
I'm getting this error for a few of my VMs as well. Still hoping someone can confirm this is a bug and that it's not a problem to move the machines into the appropriate resource pools.
Hey Spence,
I read somewhere that it was a bug, I moved mine back into the resource pools one at a time and watched them when I did, and everything turned out for the best.
Matthew
I did this because I thought I remember reading that it was a bug somewhere.
Kaizen!
Also having the same issue..... How has this not been fixed in 3 years? I think I might lodge a call with VM support and see what they say....
Hi Guys
I have a same issue, Anybody got any updates yet? I am on ESX 3.5 u4
Cheers
Im getting this also on vSphere 4.0u1.
I am trying to move from our "R&D" resource pool which limits resources to one that doesnt limit. My error says my machine will be entitled to 0% of the CPU resources. I look at the machine settings and they are all basic default settings.
FAIL
thats no good on VMware's part!! anyway, in 3.5 I did not have any issues after moving VM....
I moved them around and they had no problems either so definitely a bug in the error message!
Ryan Hoffmann | Sr. Systems Administrator | Cellcom | 1580 Mid Valley Dr. | Ph: 920-617-6831 | Email: ryan.hoffmann@cellcom.com | cellcom.com
Cellcom is an Nsight Company
I get this still with the latest ESXi 4.1 U1 348481
Its definately a BUG - not sure if there is a KB on it - workaround I documented:
http://www.vmadmin.info/2011/04/cpu-resource-shares-bug.html
I 'm getting the same error with ESX4.1U1.
But there is a KB for that issue : http://kb.vmware.com/kb/1018360
Hi everyone,
Well, this very discussion about the "CPU Resource Shares BUG" was started in 2007 for "VMware Infrastructure 3". We're now in February 2012, and I'm now getting the same erroneous error message, when moving a Virtual Machine between two resource pools (with custom shares), using VMware vCenter Server 4.1 Update 1, running a HA/DRS Cluster of several hosts running ESXi 4.1Update 1, namely the following error message:
The CPU resource shares for VMxyz are much lower than the virtual machine's in the resource pool.
With its current share settings, this virtual machine will be entitled to 0% of the CPU resources in the pool. Do you want to continue?
[Yes] [No]
I have also found the KB article that user "ideFix1505" has kindly pointed out, namely:
I also entered a similar note in the "feedback" text area for the KB article page - http://kb.vmware.com/kb/1018360 - Let's see if this helps! :smileyconfused:
Maybe it's a good idea if other users also ask for the same "feature request"? Hint! Hint!
Cheers,
Ricardo
Still this issue exist , verified & reproduced in vSphere 5.5 update 2 .
VMware Team : what is the update of this ?!
still exist in vCenter 6.0 U3c