Re: [one-users] (OpenNebula 2.0.1 - VMWare ESXi 4.1)
Hi Tino, About the 64 bit guest OS I think that the hardware that I have for the ESXi hypervisors is not suited for that kind of architecture. I tested the execution of a 64 bit environment on my ESXi cluster nodes using VMWare VSphere Client and when it launches the VM it tells me that it can run 64 bit architecture. I just wanted to know if someone has tested OpenNebula and esxi 4.1 with 64 bit guest OSes because I can't with my setup. On Wed, Feb 16, 2011 at 4:22 PM, Tino Vazquez tin...@opennebula.org wrote: Hi Luigi, AFAIK, there shouldn't be no problems running 64 bit guests. What is the error message? Regards, -Tino -- Constantino Vázquez Blanco, MSc OpenNebula Major Contributor / Cloud Researcher www.OpenNebula.org | @tinova79 On Wed, Feb 16, 2011 at 11:15 AM, Luigi Fortunati luigi.fortun...@gmail.com wrote: Hi, I'm using OpenNebula 2.0.1 with ESXi 4.1 cluster nodes. Up to now I've tested the usage of i686 guest OS architecture and it works fine. However it seems impossible to define and use VM templates that uses 64 bit guest OS. Is it true? Have you tested the deployment of 64 bit guest os with OpenNebula and ESXi 4.1? -- Luigi Fortunati ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Luigi Fortunati ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] (OpenNebula 2.0.1 - VMWare ESXi 4.1)
Hi, I'm using OpenNebula 2.0.1 with ESXi 4.1 cluster nodes. Up to now I've tested the usage of i686 guest OS architecture and it works fine. However it seems impossible to define and use VM templates that uses 64 bit guest OS. Is it true? Have you tested the deployment of 64 bit guest os with OpenNebula and ESXi 4.1? -- Luigi Fortunati ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Incomplete information from hosts polling (VMWare ESXi 4.1 an OpenNebula 2.0.1)
Thanks Tino! In contrast with what it's written on the documentation *it is possible* to connect to the ESXi hypervisors machines via ssh and launch commands (but only as root user). I noticed that on the ESXi 4.1 machines that we got installed there is a nice program called esxtop which can also be executed in batch mode. That command can output more of the informations that are needed by opennebula to work and schedule VMs correctly. I believe that maybe it's a good idea to rethink the IM Driver in order to gather information about resource usage using esxtop instead of virsh commands. With the latter I didn't find a command capable of retrieving the memory usage of the hypervisor, which is 800 MB in my case. On Fri, Feb 11, 2011 at 3:10 PM, Tino Vazquez tin...@opennebula.org wrote: Hi Luigi, I've updated the ticket, I will be implementing this for the next release. Regards, -Tino -- Constantino Vázquez Blanco, MSc OpenNebula Major Contributor / Cloud Researcher www.OpenNebula.org | @tinova79 On Wed, Feb 9, 2011 at 3:14 PM, Luigi Fortunati luigi.fortun...@gmail.com wrote: Thanks Tino, That is probably more a problem of libvirt, since VMWare IM Driver use it in order to access information about the hosts. In order to get information about the hosts OpenNebula launches a virsh command and parses the output. The script that does this work is located in $ONE_LOCATION/lib/remotes/im and the output of the virsh command is: oneadmin@custom2:~/lib/remotes/im$ virsh -c esx://custom6.sns.it/?no_verify=1 nodeinfo Enter username for custom6.sns.it [root]: Enter root's password for custom6.sns.it: CPU model: AMD Opteron(tm) Processor 246 CPU(s): 2 CPU frequency: 1992 MHz CPU socket(s): 2 Core(s) per socket: 1 Thread(s) per core: 1 NUMA cell(s):2 Memory size: 2096460 kB I always get the same output, no matter how many VMs are running on the cluster node. That is why OpenNebula returns with an output like this: oneadmin@custom2:~/var/96$ onehost show 1 HOST 1 INFORMATION ID: 1 NAME : custom6.sns.it CLUSTER : default STATE : MONITORING 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 : 1 MONITORING INFORMATION CPUSPEED=1992 HYPERVISOR=vmware TOTALCPU=200 TOTALMEMORY=2096460 OpenNebula polls cluster nodes periodically and gets only information about hypervisor type, cpu frequency, total cpu, total memory size. The limitation here is caused by libvirt (virsh) which is unable to return more information about the actual usage of resources. The integration of OpenNebula with Xen can rely on ssh access to the cluster nodes. The IM Driver for Xen hypervisors, launches xentop on every cluster node in order to get information about the VMs and then parses the output. As an example here is the output of commands xm and xentop (some info is purged): custom9:/ # xentop -bi2 NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) Domain-0 -r1020.01930260 93.7 no limit n/a 2000 NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) Domain-0 -r1020.31930260 93.7 no limit n/a 2000 custom9:/ # xm info host : custom9 release: 2.6.34.7-0.5-xen version: #1 SMP 2010-10-25 08:40:12 +0200 machine: x86_64 nr_cpus: 2 nr_nodes : 2 cores_per_socket : 1 threads_per_core : 1 cpu_mhz: 1991 [...] total_memory : 2011 free_memory: 135 free_cpus : 0 max_free_memory: 1508 max_para_memory: 1504 max_hvm_memory : 1492 [...] The script $ONE_LOCATION/lib/remotes/im/xen.d/xen.rb parses those two outputs and retrieves data about memory, cpu, and network usage. I think that VMWare drivers are scarcely useful if they can't provide the degree of information which can be achieved with xen hypervisors and OpenNebula, I've tested the effects of this issue in my tests. On Tue, Feb 8, 2011 at 6:34 PM, Tino Vazquez tin...@opennebula.org wrote: Hi Luigi, There is a bug in the IM driver for VMware, is not reporting the Free memory at all. I've opened a ticket to keep track of the issue [1], it will be solved in the next release. Regards, -Tino [1] http://dev.opennebula.org/issues/481 -- Constantino
Re: [one-users] Incomplete information from hosts polling (VMWare ESXi 4.1 an OpenNebula 2.0.1)
Thanks Tino, That is probably more a problem of libvirt, since VMWare IM Driver use it in order to access information about the hosts. In order to get information about the hosts OpenNebula launches a virsh command and parses the output. The script that does this work is located in $ONE_LOCATION/lib/remotes/im and the output of the virsh command is: oneadmin@custom2:~/lib/remotes/im$ virsh -c esx:// custom6.sns.it/?no_verify=1 nodeinfo Enter username for custom6.sns.it [root]: Enter root's password for custom6.sns.it: CPU model: AMD Opteron(tm) Processor 246 CPU(s): 2 CPU frequency: 1992 MHz CPU socket(s): 2 Core(s) per socket: 1 Thread(s) per core: 1 NUMA cell(s):2 Memory size: 2096460 kB I always get the same output, no matter how many VMs are running on the cluster node. That is why OpenNebula returns with an output like this: oneadmin@custom2:~/var/96$ onehost show 1 HOST 1 INFORMATION ID: 1 NAME : custom6.sns.it CLUSTER : default STATE : MONITORING 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 : 1 MONITORING INFORMATION CPUSPEED=1992 HYPERVISOR=vmware TOTALCPU=200 TOTALMEMORY=2096460 OpenNebula polls cluster nodes periodically and gets only information about hypervisor type, cpu frequency, total cpu, total memory size. The limitation here is caused by libvirt (virsh) which is unable to return more information about the actual usage of resources. The integration of OpenNebula with Xen can rely on ssh access to the cluster nodes. The IM Driver for Xen hypervisors, launches xentop on every cluster node in order to get information about the VMs and then parses the output. As an example here is the output of commands xm and xentop (some info is purged): custom9:/ # xentop -bi2 NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) Domain-0 -r1020.01930260 93.7 no limit n/a 2000 NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) Domain-0 -r1020.31930260 93.7 no limit n/a 2000 custom9:/ # xm info host : custom9 release: 2.6.34.7-0.5-xen version: #1 SMP 2010-10-25 08:40:12 +0200 machine: x86_64 nr_cpus: 2 nr_nodes : 2 cores_per_socket : 1 threads_per_core : 1 cpu_mhz: 1991 [...] total_memory : 2011 free_memory: 135 free_cpus : 0 max_free_memory: 1508 max_para_memory: 1504 max_hvm_memory : 1492 [...] The script $ONE_LOCATION/lib/remotes/im/xen.d/xen.rb parses those two outputs and retrieves data about memory, cpu, and network usage. I think that VMWare drivers are scarcely useful if they can't provide the degree of information which can be achieved with xen hypervisors and OpenNebula, I've tested the effects of this issue in my tests. On Tue, Feb 8, 2011 at 6:34 PM, Tino Vazquez tin...@opennebula.org wrote: Hi Luigi, There is a bug in the IM driver for VMware, is not reporting the Free memory at all. I've opened a ticket to keep track of the issue [1], it will be solved in the next release. Regards, -Tino [1] http://dev.opennebula.org/issues/481 -- Constantino Vázquez Blanco, MSc OpenNebula Major Contributor / Cloud Researcher www.OpenNebula.org | @tinova79 On Tue, Feb 8, 2011 at 12:56 PM, Luigi Fortunati luigi.fortun...@gmail.com wrote: Ok, I tried some tests today. The hardware/software environment includes 2 cluster nodes (ESXi 4.1), 2Gb of RAM, 2 AMD Opteron 246 Processors (2GHz), trial version licenses. The opennebula installation is self-contained. 800MB of memory are used by the hypervisor itself (that info comes from vSphere Client) so only 1,2 GB are free, but OpenNebula seems unaware of that :-( oneadmin@custom2:/srv/cloud/templates/vm$ onehost list ID NAME CLUSTER RVM TCPU FCPU ACPUTMEMFMEM STAT 2 custom7.sns.itdefault0200200200 2G 0K on 1 custom6.sns.itdefault0200200200 2G 0K on oneadmin@custom2:/srv/cloud/templates/vm$ 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
[one-users] RestrictedVersion Error (OpenNebula and VMWare ESXi 4.1 free license)
Hi, I'm posting this just to inform the community that the VMWare ESXi hypervisor 4.1 *with the free license* cannot work with OpenNebula 2.0.1 (and VMWare Driver 1.0). When you set the free license on the ESXi hypervisor through vSphere Client you lose some of the functionalities of the product and, whenever you start a VM with OpenNebula, the VM log produce this error message: Tue Feb 8 15:39:03 2011 [VMM][D]: Message received: LOG - 95 Command execution fail: /srv/cloud/one/lib/remotes/vmm/vmware/deploy custom7.sns.it/srv/cloud/one/var/95/deployment.0 Tue Feb 8 15:39:03 2011 [VMM][D]: Message received: LOG - 95 STDERR follows. Tue Feb 8 15:39:03 2011 [VMM][D]: Message received: LOG - 95 [VMWARE] cmd failed [/srv/cloud/one/bin/tty_expect -u oneadmin -p custom2011 virsh -c esx://custom7.sns.it?no_verify=1 define /srv/cloud/one/var/95/deployment.0]. Stderr: Tue Feb 8 15:39:03 2011 [VMM][D]: Message received: LOG - 95 error: Failed to define domain from /srv/cloud/one/var/95/deployment.0 Tue Feb 8 15:39:03 2011 [VMM][D]: Message received: LOG - 95 error: internal error HTTP response code 500 for call to 'RegisterVM_Task'. Fault: ServerFaultCode - *fault.RestrictedVersion.summary* Tue Feb 8 15:39:03 2011 [VMM][D]: Message received: LOG - 95 Tue Feb 8 15:39:03 2011 [VMM][D]: Message received: LOG - 95 . Stdout: ExitCode: 1 Tue Feb 8 15:39:03 2011 [VMM][D]: Message received: LOG - 95 ExitCode: 1 Tue Feb 8 15:39:03 2011 [VMM][D]: Message received: DEPLOY FAILURE 95 - *This only happens when the free license is set on the hypervisor*. -- Luigi Fortunati ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Incomplete information from hosts polling (VMWare ESXi 4.1 an OpenNebula 2.0.1)
On Fri, Feb 4, 2011 at 10:35 AM, Luigi Fortunati luigi.fortun...@gmail.comwrote: To Siva: As far as I know you can connect to the ESXi Server in three ways: libvirt and virsh (the way of OpenNebula-VMWare Driver): The VMWare Driver of OpenNebula uses virsh commands (which relies on libvirt) to access some hypervisor functionalities. You can use directly virsh commands to test what libvirt is capable of by using this command: virsh -c esx://[user@]hostname of hypervisor/?no_verify=1 Then you'll get a password prompt. you can use root as user. no_verify=1 disables check on certificates. You can find other useful infos here: http://libvirt.org/drvesx.html If OpenNebula can't connect you'll probably notice some error messages on the logs. Take a look in var/oned.log and var/vm id/vm.log and post the errors, otherwise check the installation steps in the VMWare Driver section of the documentation. I remember that you have to configure a username and password in a file in order to let OpenNebula connect to hypervisors through virsh. VMWare API (vSphere Client): ESXi hosts come with a public API developed by VMWare for accessing hypervisor functionalities: http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/ I think that libvirt actually uses ver. 2.5 of those APIs. vSphere Client most probably connects to the hypervisor using those API (probably the latest version of the latter). Shell: You have to enable access to the shell through VSphere Client. As far as I know it is only possible to make ssh access with the root credentials, even if you created other users and modified /etc/passwd file to set a shell for the user. On Fri, Feb 4, 2011 at 7:33 AM, Siva Prasad myknowinm...@gmail.comwrote: Hi Can you please let me know how are you able to connect to ESXI Server.I tried the same but got the error connection refused. Please let me know the detail steps. Thanks, Siva On Thu, Feb 3, 2011 at 9:40 PM, Luigi Fortunati luigi.fortun...@gmail.com 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 ACPUTMEMFMEM STAT 2 custom7.sns.itdefault0200200200 2G 0K off 1 custom6.sns.itdefault2200200200 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 Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Luigi Fortunati -- Luigi Fortunati ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Incomplete information from hosts polling (VMWare ESXi 4.1 an OpenNebula 2.0.1)
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 rube...@dacya.ucm.eswrote: 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 luigi.fortun...@gmail.com 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 ACPUTMEMFMEM STAT 2 custom7.sns.itdefault0200200200 2G 0K off 1 custom6.sns.itdefault2200200200 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 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 -- Luigi Fortunati ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Problems when booting VM (OpenNebula 2.0.1 and ESXi 4.1)
-datacenterdsName=images Does it mean that it can't upload the vmx file to the given folder? This problem is probably more related to libvirt. I found good information about libvirt and esx here: http://libvirt.org/drvesx.html (this may helps you as it has for me) Can someone post a deployment.0 file of a vm correctly launched either with persistent and nonpersistent image? P.S.: Another thing I noticed is that the vm doesn't get scheduled on a cluster host if you don't set the number of vcpu on the vm template file! On Tue, Feb 1, 2011 at 2:37 PM, Matthias Keller mkel...@upb.de wrote: Dear Luigi, referring to your last post today (01.02), I might help. We are in the same situation as we also trying to build up an Opennebula-Cloud with ESXi-Servers. After some headache about my low administration skills and about a bit unclear documentation on the website / configuration process, we figured out to launch VMs on esx-servers. As I'm not able to diagnose your described issues, I try to summaries our experiences: - we had to reinstall our opennebula 2 installment, because system-wide installation /etc/oned.conf, etc. didn't work fully, because some scripts and especially scripts of the esx-drivers plugin. So our second try ends - as your installment - in /srv/cloud/one - after new logging in ONE_LOCATION env was not set correctly, so we had to make sure it's written somewhere at .bashrc and changing user from root by using su - oneadmin, this initializes the oneadmin-shell environment - first we tried starting a vm without network to minimize the error-sources. - we installed (in documentation mentioned) script-fix with sudo rights - this is need to change owner, so the oneadmin of esx is able to access it, in order to start your vm - I guess somewhere near starting a vm can your problem be solved. - the [image] esx volume should be the correct one (DATASTORE) and can be checked via vsphere client. the oneadmin has to have the same uid in esx and linux. We also checked this, by starting a placed VM by hand via vsphere client. - describing Arch=i686 is necessarily (as you did). - activate logging for VMM-Driver (because I assume your TM-Driver works properly): if your oned.conf looks like: # VMware Driver Addon Virtualization Driver Manager Configuration #--- VM_MAD = [ name = vmm_vmware, executable = one_vmm_sh, arguments = vmware, default= vmm_sh/vmm_sh_vmware.conf, type = vmware ] than the file should contains the following input: file:/srv/cloud/one/etc/vmm_sh/vmm_sh_vmwarerc # Uncomment the following line to active MAD debug ONE_MAD_DEBUG=1 For every driver it should work with editing the following file - but I'm not really sure about that: /srv/cloud/one/etc/defaultrc Logs are placed in /srv/cloud/one/var Perhaps I could helped you, Matthias Keller -- Luigi Fortunati ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Incomplete information from hosts polling (VMWare ESXi 4.1 an OpenNebula 2.0.1)
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 ACPUTMEMFMEM STAT 2 custom7.sns.itdefault0200200200 2G 0K off 1 custom6.sns.itdefault2200200200 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 Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] open-nebula front-end hardware requirements
Hi, I'm planning to build a cloud infrastructure based on open nebula 2.0.1 and vmware hypervisors (ESXi 4.1 Free). However I couldn't find any useful information either on the open-source or the commercial project websites about minimum or recommended hardware requirements for the computer that will host the Open Nebula Front-end. Do you have any suggestion on this point? -- Luigi Fortunati ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
