search for: yuanle

...to destroy (or rebuild) dead instance without rebooting the hypervisor. Any suggestions is welcome. The software I am running: hypervisor os: ubuntu 12.04.3 hypervisor kernel: 3.8.0-35-generic vm os: ubuntu 12.04 vm kernel: 3.2.0-56-virtual openstack: havana libvirt: 1.1.1-0ubuntu8~cloud2 Thanks, Yuanle

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.

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. If setting vcpu# is not effective for LXC container, you may need to use cgroups. -- Thanks, Yuanle On Mon, Mar 17, 2014 at 2:32 PM, WANG Cheng D < Cheng.d.Wang@alcatel-sbell.com.cn> 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...

Hi I tried to restrict usage of some running VM by cpu.shares (i.e. set to 10 from original 1024) on loaded system and it seem doesn't work as I expected... all running processes has same CPU usage (by htop) :-/ Does anyone has same experience? Fedora 19, libvirt-1.0.5.9-1.fc19.x86_64 Thanks a lot Martin -- Martin Pavlásek <mpavlase@redhat.com> OpenStack QA Associate/Red Hat