VMware Cloud Community
virtual_Vic
Contributor
Contributor

VirtualCenter issue with shares set to custom

Hello all,

After I upgraded our VirtualCenter to 2.5, all the VMs shares get set to "custom" for both CPU and Memory. They all get set pretty low too and causes the VMs to perform badly. I went through and set them all back to normal.

Has any one else experienced this after upgrading from 2.0 to 2.5?

Cheers,

-VMVic

Reply
0 Kudos
9 Replies
piercelynch
Enthusiast
Enthusiast

I had no problems with the resource pooling and resource shares after upgrading on quite a few VCs.... not heard of that one before. So all the share limits were also different values after the upgrade?

Reply
0 Kudos
virtual_Vic
Contributor
Contributor

That is correct. We really dont use resource pools, as we were really using them to group like VMs together and yes, Shares were all custom and very low. For example, by default if all the VMs in our environment are set to "normal" then they all get value of 4000, but after the upgrade we had "custom" and all different. Some were 250, some were 177... just weird numbers like that.

-VMVic

Reply
0 Kudos
garybrown
Enthusiast
Enthusiast

Yes, just to confirm you are not alone with this issue we too have exactly the same problem - bizarre values assigned, 888, 893 1777 are some examples - painful !!

Reply
0 Kudos
bretti
Expert
Expert

I'm glad I ran into this post. We are having the same thing happen over here. So far no complaints of performance issues though. The numbers are all over the board.

Reply
0 Kudos
piercelynch
Enthusiast
Enthusiast

Wooo... thats really very weird! To be honest guys.. I would open a ticket with VMWare Support - that really isn't a good thing to be happening because of an upgrade :S

P.

Reply
0 Kudos
bretti
Expert
Expert

Yeah, tell me about it. That could of had devastating results depending on the numbers.

Reply
0 Kudos
dinny
Expert
Expert

Hiya,

This appears to be a known issue with DRS (not sure if just with VC 2.5?)

See:

http://communities.vmware.com/message/869311

The KB article isn't very specific - but perhaps the workaround specified will stop it.

(I haven't tried it myself yet...)

Dinny

Reply
0 Kudos
virtual_Vic
Contributor
Contributor

impensb,

Mine show up random as well, except that I had a multitude of VMs showing share values very low... some as low as 75, down from the normal 4000.

-VM Vic

Reply
0 Kudos
virtual_Vic
Contributor
Contributor

I'm feeling the pain... I have 1500 VMs running across 100 hosts split into to physical locations....aarrrggh.

Virtual Vic

Reply
0 Kudos