Currently, if you really want to overcommit RAM, there is a workaround with KVM, but it involves to modify the value reported by the host directly in the database.
On Wed, Jul 17, 2013 at 12:14 PM, Tao Lin <[email protected]> wrote: > Hi,Andreas, > Memory over-committing has not been support yet.Take a look at the > following links: > > > [1] http://markmail.org/message/u6i5mdwyf42icsff > [2] https://cwiki.apache.org/CLOUDSTACK/cpu-and-ram-overcommit.html > > > 2013/7/17 Andreas Huser <[email protected]> > > > Hello at all, > > > > i have two KVM Hypervisors with equal RAM à 16GB > > In the Cloudstack zone resource tab can i read "Allocated: 15.30 GB / > > 31.13 GB". > > > > When i configure memory overcommit *2 and restart the Cloud Manager. I > see > > the same "Allocated: 15.30 GB / 31.13 GB" > > Must this not now like e.g "Allocated: 15.30 GB / 62.26GB" to be? > > > > many thanks > > Regards Andreas > > > > > > > > > > > > Mit freundlichen Grüßen > > > > Andreas Huser > > Geschäftsführer > > System Engineer / Consultant > > (Cisco Certified Solaris, Linux) > > > > --------------------------------------- > > Zellerstraße 28 - 77654 Offenburg > > Tel: +49(781) 1278689 0 > > Mobil: +49(176) 10308549 > > [email protected] > > > > > > > > > > > -- *Arnaud Gaillard* CTO Mobile : +41 78 674 58 95 <https://docs.google.com/file/d/0B2iGziD9SUPURU0yRjhSX1JhU0k/edit?usp=sharing>
