Hi,
On Mon, Apr 29, 2013 at 5:15 PM, Christoph Pleger <
christoph.ple...@cs.tu-dortmund.de> wrote:
> Hello,
>
> > We have the "logical" OpenNebula level enforcement, and the hypervisor
> > level.
> >
> > First one: the OpenNebula scheduler will not allocate more cpu/memory
> than
> > the Host rep
Hello,
> We have the "logical" OpenNebula level enforcement, and the hypervisor
> level.
>
> First one: the OpenNebula scheduler will not allocate more cpu/memory than
> the Host reports as available.
>
> Hypervisor level reservation: cgroups for kvm, credit scheduler for xen,
> and the esx cpu sc
Hi,
On Fri, Apr 26, 2013 at 11:27 AM, Christoph Pleger <
christoph.ple...@cs.tu-dortmund.de> wrote:
> Hello,
>
> > I'm not that much familiar with cgroups, but the way I understand it the
> first VM does not get 100%, it will get 1024 shares out of 1536 (2/3 of
> cpu
> > time).
>
> Yes, that's ho
Hello,
> I'm not that much familiar with cgroups, but the way I understand it the
first VM does not get 100%, it will get 1024 shares out of 1536 (2/3 of
cpu
> time).
Yes, that's how cgroup works, and I wonder why this is not a conflict with
what CPU= in VM Templates means and why the documentati
Hi there,
On Fri, Apr 26, 2013 at 9:09 AM, Christoph Pleger <
christoph.ple...@cs.tu-dortmund.de> wrote:
> Hello,
>
> > I have a new question about that.
> >
> > On http://opennebula.org/documentation:rel3.8:kvmg, I read about
> cgroups:
> >
> > "So, thanks to cgroups a VM with CPU=0.5 will get h
Hello,
> I have a new question about that.
>
> On http://opennebula.org/documentation:rel3.8:kvmg, I read about cgroups:
>
> "So, thanks to cgroups a VM with CPU=0.5 will get half of the physical CPU
> cycles than a VM with CPU=1.0."
>
> How can a second VM get half of the physical CPU cycles of a
Hello,
> HOST/CPU is the number of cores reported by the hypervisor x 100; 800 = 8
> cpu cores.
> VM Template CPU is the number of Host CPU cores reserved for the VM. So
> cpu=0.5 means that the Host will allocate 50 from the CPU total for that
> VM.
I have a new question about that.
On http://o
Hi,
HOST/CPU is the number of cores reported by the hypervisor x 100; 800 = 8
cpu cores.
VM Template CPU is the number of Host CPU cores reserved for the VM. So
cpu=0.5 means that the Host will allocate 50 from the CPU total for that VM.
VM Template VCPU is the number of virtual cores the VM guest
Hello,
from the documentation, it is not clear for me how real CPUs in the cloud
nodes, the number of virtual CPUs for a VM and the CPU percentage for a VM
are related to each other. Can someone explain that, please?
Regards
Christoph
___
Users maili
