Hi, did you figure this out? It sounds like you are changing global settings (mem.overprovisioning.factor) which I believe is not correct. These settings exist in previous versions and (despite the name) are for controlling reservations. I believe the new overcommit settings are configured at the cluster level.
Best regards, Kirk On 08/23/2013 09:08 AM, Sean Hamilton wrote: > Hey guys, > > I'm playing around with 4.2 and VMware vSphere (version 5.0). > We're interested in memory overcommit, but the observed behaviour isn't > what I expected. > > I'm seeing my instances being created in vCenter with a memory reservation > that is equal to the configured memory. If I then change the overcommit > setting to 2.0 I see instances being created with a reservation that is > half of the configured memory. > > There is a global setting of vmware.reserve.mem that is set to false, but I > don't see it making a difference. I get the same behaviour if it's true or > false. > > Can anyone help? > > Thanks, > Sean >
