Hi, You can guide the overcommitment by using the CPU attribute of the template. For example if you want to put 16 VMs in nebula02 with 8 cores, just define the VMs with
CPU = 0.5 If you need those VMs to have 2 virtual cores use: CPU=0.5 VCPU=2 Cheers Ruben On Wed, May 4, 2011 at 4:32 PM, Giovanni Toraldo <g...@libersoft.it> wrote: > Hi, > > I noticed only now that I've exhausted my opennebula available CPU > resources: > > > ID NAME CLUSTER RVM TCPU FCPU ACPU TMEM FMEM > STAT > > 2 nebula01 default 2 400 369 0 11.8G 10.7G > on > > 3 nebula02 default 4 800 792 0 11.8G 7.4G > on > > 4 nebula03 default 4 800 796 0 11.8G 9.9G > on > > 5 nebula04 default 4 800 774 0 11.8G 10.4G > on > > However CPU isn't really used so much. There is a way to let the > scheduler allocate new VM? I supposed that using RANK = FREEMEMORY in VM > template should solve, but not. > > Any hints? > > -- > Giovanni Toraldo > http://www.libersoft.it/ > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > -- Dr. Ruben Santiago Montero Associate Professor (Profesor Titular), Complutense University of Madrid URL: http://dsa-research.org/doku.php?id=people:ruben Weblog: http://blog.dsa-research.org/?author=7
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org