Hello, Could you describe the problem you had? By default the scheduler will not overcommit cpu nor memory.
Bye On Thu, Oct 28, 2010 at 4:50 AM, Shashank Rachamalla <[email protected]> wrote: > Hi > > We have a requirement where in the scheduler should not allow memory over > committing while choosing a host for new vm. In order to achieve this, we > have changed the way in which FREEMEMORY is being calculated for each host: > > FREE MEMORY = TOTAL MEMORY - [ Sum of memory values allocated to VMs which > are currently running on the host ] > > Please let us know if the above approach is fine or is there any better way > to accomplish the task. We are using opennebula 1.4. > > -- > Regards, > Shashank Rachamalla > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > -- Javier Fontan, Grid & Virtualization Technology Engineer/Researcher DSA Research Group: http://dsa-research.org Globus GridWay Metascheduler: http://www.GridWay.org OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
