Re: 4.2 VMware memory overcommit

2013-09-10 Thread Sean Hamilton
Using the latest build fixed this issue for me. Thank you. On 10 September 2013 06:48, Harikrishna Patnala < harikrishna.patn...@citrix.com> wrote: > Hi, > > There was a bug opened on this global parameter vmware.reserve.mem( > https://issues.apache.org/jira/browse/CLOUDSTACK-4498) and it was fi

Re: 4.2 VMware memory overcommit

2013-09-09 Thread Harikrishna Patnala
Hi, There was a bug opened on this global parameter vmware.reserve.mem(https://issues.apache.org/jira/browse/CLOUDSTACK-4498) and it was fixed. Can you please try with latest 4.2. -Harikrishna On 23-Aug-2013, at 9:38 PM, Sean Hamilton wrote: > Hey guys, > > I'm playing around with 4.2 and V

Re: 4.2 VMware memory overcommit

2013-09-09 Thread Dean Kamali
I know this may sound silly, but I haven't found clear instructions on how to setup CS 4.2 "without deb packages" can some provide me with some insight on how to set it up. Thank you

Re: 4.2 VMware memory overcommit

2013-09-09 Thread Kirk Kosinski
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