[one-users] Placement section
Carlos Martín Sánchez
cmartins at fdi.ucm.es
Mon Sep 20 02:41:05 PDT 2010
The PLACEMENT attribute you are using is ignored by the scheduler (take a
look at the examples in the link you provided). Try with
REQUIREMENTS = "HYPERVISOR = \"kvm\""
If you are using the development version, you may want to try the new host
clustering feature  instead of using the hypervisor attribute.
Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
OpenNebula Open Source Toolkit for Cloud Computing:
On 20 September 2010 10:18, Ruben Diez <rdiez at cesga.es> wrote:
> We are watching for a xen/kvm mixed set of nodes. For do this, we create
> the hosts in the following manner:
> - For xen nodes: onehost create 220.127.116.11 im_xen vmm_xen tm_ssh
> - For kvm nodes: onehost create 18.104.22.168 im_kvm vmm_kvm tm_ssh
> So, for select to run a VM in a kvm or xen node type we are using the
> "PLACEMENT" section in the following manner:
> PLACEMENT = [
> REQUIREMENTS = "HYPERVISOR = \"kvm\""
> According with http://www.opennebula.org/documentation:rel2.0:template the
> "HYPERVISOR" variable is defined by default....
> But it don work: the scheduler deploy the VM in a xen node....
> Where are the error?? Any other manner to force a VM to be deployed in a
> xen or kvm node???
> Users mailing list
> Users at lists.opennebula.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users