Hi,
I'm not libvirt expect. My guess is that some vcpu settings only apply to KVM/qemu backend. LXC is quite different from them.
I'm not libvirt expect. My guess is that some vcpu settings only apply to KVM/qemu backend. LXC is quite different from them.
If setting vcpu# is not effective for LXC container, you may need to use cgroups.
--
Thanks,
On Mon, Mar 17, 2014 at 2:32 PM, WANG Cheng D <Cheng.d.Wang@xxxxxxxxxxxxxxxxxxxx> wrote:
Dear all,
I am not clear about the ‘vcpu’ element for CPU allocation. I allocated 1 vCPU to my container, after I started the container, I ran 4 computation-intensive tasks on the container. And I found all the 4 physical core are 100% used (my host has 4 physical cores and no other application ran on the host except the container). That is, all available cores were used by the container. I want to know how to give a hard limitation for CPU usage of a container.
So I don’t understand what ‘vcpu’ setting can be used for.
I know that another CPU allocation element ‘shares’ can also be used, but this elements only give a relative quota. If new containers are started, the CPU quota for the already started containers will change.
Regards,
Cheng
_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
