I can post the VM template content on monday. However, as far as I remember, the vm template was really simple: NAME="Debian" VCPU= 2 MEMORY=1024 DISK=[IMAGE="Debian5-i386"] OS=[ARCH=i686]
The VMs can boot and run, I can log on console through vSphere Client on the newly created VMs. I noticed that if you don't declare the number on VCPU the VM doesn't get scheduled on a cluster node. This option seems mandatory but I didn't find any mention about it on the documentation. Another thing that seems mandatory is declaring the cpu architecture as i686, otherwise OpenNebula will return error when writing the deployment.0 file. On Thu, Feb 3, 2011 at 5:42 PM, Ruben S. Montero <[email protected]>wrote: > Hi, > > I am not sure this is related to the VMware monitoring... Can you send the > VM Templates? > > Thanks > > Ruben > > On Thu, Feb 3, 2011 at 5:10 PM, Luigi Fortunati <[email protected] > > wrote: > >> Hi, >> I noticed a serious problem about the usage of VMWare ESXi 4.1 and >> OpenNebula 2.0.1. >> I'm actually using the VMWare driver addon which can be found on the >> opennebula website (ver. 1.0) and libvirt (ver. 0.8.7). >> It happens that OpenNebula can't get information about the usage of >> resources on the cluster nodes. >> By running 2 VM (each one requires 2 VCPU and 1 GB of memory) and >> executing some commands I get this output. >> >> oneadmin@custom2:~/src$ onehost list >> ID NAME CLUSTER RVM TCPU FCPU ACPU TMEM FMEM >> STAT >> 2 custom7.sns.it default 0 200 200 200 2G 0K >> off >> 1 custom6.sns.it default 2 200 200 200 2G 0K >> on >> oneadmin@custom2:~/src$ onehost show 1 >> HOST 1 INFORMATION >> >> ID : 1 >> NAME : custom6.sns.it >> CLUSTER : default >> STATE : MONITORED >> IM_MAD : im_vmware >> VM_MAD : vmm_vmware >> TM_MAD : tm_vmware >> >> HOST SHARES >> >> MAX MEM : 2096460 >> USED MEM (REAL) : 0 >> USED MEM (ALLOCATED) : 0 >> MAX CPU : 200 >> USED CPU (REAL) : 0 >> USED CPU (ALLOCATED) : 0 >> RUNNING VMS : 2 >> >> MONITORING INFORMATION >> >> CPUSPEED=1992 >> HYPERVISOR=vmware >> TOTALCPU=200 >> TOTALMEMORY=2096460 >> >> As you can see OpenNebula is unable to get correct information about the >> usage of resources on the cluster nodes. >> As these informations are used by the VM scheduler, OpenNebula is unable >> to schedule the VM correctly. >> I tried to create several VM and all of them were placed on the same host >> even if the latter was unable to satisfy the resource requirements of all >> the VMs. >> I think that this problem is strongly related to libvirt as OpenNebula use >> it to recover information about hosts and vm. >> >> Do you get the same behavior? Do you know if there is a way to solve this >> big issue? >> >> -- >> Luigi Fortunati >> >> _______________________________________________ >> Users mailing list >> [email protected] >> 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 > -- Luigi Fortunati
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
