On 09/05/2011 00:36, Ruben S. Montero wrote:
No, the host will see the same CPU speed. The CPU attribute in the
template is only for OpenNebula and the scheduler.
OK :)
Maybe some sort of clarification should be placed in the documentation
(http://opennebula.org/documentation:rel2.2:template)
Hi Carlos,
Which bug are you referring to? AFAIK, the CPU parameter is only used
by the scheduler, and the VMware integration does honor the VCPU
paremeter, so overcommitment should work as expected.
Regards,
-Tino
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
If you submit a template using the CPU parameter, the virtual machine
never is deployed in to a VMWare machine. If you use VCPU instead, it is
properly deployed...
El 09/05/11 14:18, Tino Vazquez escribió:
Hi Carlos,
Which bug are you referring to? AFAIK, the CPU parameter is only used
by
Hi,
That bug should be solved in the latest release (2.2.0). It is related
to this [1] bug, now the CPu is equally inferred (it isn't provided by
libvirt).
Regards,
-Tino
[1] http://dev.opennebula.org/issues/481
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
ok, I thought that patch was related to only memory issues.
El 09/05/2011 17:16, Tino Vazquez escribió:
Hi,
That bug should be solved in the latest release (2.2.0). It is related
to this [1] bug, now the CPu is equally inferred (it isn't provided by
libvirt).
Regards,
-Tino
[1]
Hi
I already tried CPU setting, but the guest will see half of the real
frequency of my host CPU: this isn't cpu overcommit, I am just saying to
allocate half of my 8 cpu to that VM (or not?).
No, the host will see the same CPU speed. The CPU attribute in the template
is only for OpenNebula
Il 04/05/2011 18:39, Ruben S. Montero ha scritto:
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
I already tried CPU setting, but the guest will see half of the
Hi,
I noticed only now that I've exhausted my opennebula available CPU
resources:
ID NAME CLUSTER RVM TCPU FCPU ACPUTMEMFMEM STAT
2 nebula01 default2400369 0 11.8G 10.7G on
3 nebula02 default4800792
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,
there was a bug about the CPU template parameter that was not working
for vmware so it was needed to use VCPU instead. Thus, I have no way to
manage the overcommitment of VMs to a host.
Is this issue solved in the current version? (i have noticed that memory
issues are supposed to be
10 matches
Mail list logo
