Hi, Yes indeed this is a bug. As you suggest resources should not be freed, in fact image and network resources are not released. The idea was to do the same with the host resources as well.
Thanks for the catch up! Cheers Ruben For your reference: http://dev.opennebula.org/issues/1335 On Tue, Jul 3, 2012 at 12:10 PM, cmcc.dylan <[email protected]> wrote: > Hello everyone: > I am very confused opennebula will release the resources of the vm > when it is suspended. It is clear that this design will lead to a problem > when the vm will resume again but the host os has no enough resources to > run it, for example, no enough memory. > Currently，It looks likely scheduler only deal with "deploy action" and > the scheduler is the only place to judge whether there are sufficient > resources in the host. So when executing a "migarate action", it doesn't > to judge because scheduler doesn't deal with "migarate action". The > "migarate action" is successful although there aren't enough resources in > the target host os according to the opennebula resources statistical > algorithms. > > I'm not sure I understand it right. Please someone can help me! > > > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - The Open Source Solution for Data Center Virtualization www.OpenNebula.org | [email protected] | @OpenNebula
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
