similar to: Libvirt LXC vcpu doesn't seem to work

Hi, We are using Openstack and Libvirt/LXC as our virtualization endpoint. Here is an example of one of our libvirt domain: http://paste.debian.net/167276/ So we have <vcpu>4</vcpu>. But the command : root at PAR-SRV-02-MASTER:/etc/libvirt/lxc# virsh --connect lxc:/// dominfo instance-0000004a Id: 17495 Name: instance-0000004a UUID:

Hi folks! i created a server with this XML file: <domain type='lxc'> <name>lxctest1</name> <uuid>227bd347-dd1d-4bfd-81e1-01052e91ffe2</uuid> <metadata> <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> <libosinfo:os id="http://centos.org/centos/6.9"/>

Dear all I allocate only one vcpu for the container by the following statement, that is, I want to pin the vcpu to physical core "2". <vcpu placement='static' cpuset="2" >1</vcpu> My host has 4 physical cores. Before test, all the 4 cores are idle. After I run 4 processes in the container, I found all the 4 cores in the host are 100% used. That is, the

Hi Gao feng, I noticed one of your patch which adds cpuset cgroup support for lxc have been merged in libvirt 1.0.4. But I can't find any virsh command to set cpusettune for lxc container. Is there anyone? And how can I configure cpusettune for lxc container lively? Thanks ------------------ Best regards! GuanQiang

Dear all, I want my container to run on the third CPU core and I define this by the following xml scrpits: <vcpu placement="static" cpuset="3">1</vcpu> When I run my application in a container terminal, I can see the application runs on the third core as expected. When I run my application using lxc-enter-namespace, the CPU pinning doesn't take effect, i.e.,

Hi, I'm running OpenStack to manage LXC instance through libvirt. The same setting runs perfectly well on Ubuntu 12.04, while on CentOS 6u3, libvirt dumped following message when starting lxc instance. virsh -c lxc:/// start instance-00000032 error: internal error The 'cpuacct', 'devices' & 'memory' cgroups controllers must be mounted Really appreciated if

Hi,guys! I've been using libvirt-1.1.1 with LXC1.0.0 to do my CS homework.But I met a problem when I tried to set vcpu for a LXC.The /sys/fs/cgroup/cpuset/machine/cpuset.cpus always show 0-3 no matter how many vcpu I defined in the XML setting file. But I found the command "virsh -c lxc:/// domaininfo lxc_name" got the right number as it is defined. What's the problem there? Is

Hello! How do i get pass this error? offlinehacker:~/ $ virsh --debug 0 -c lxc:/// create o1.xml create: file(optdata): o1.xml error: Failed to create domain from o1.xml error: internal error: No valid cgroup for machine c1 My cgroups seem to be mounted: cgroup on /sys/fs/cgroup/systemd type cgroup

Hi all Each lxc container on node have mounted tmpfs for cgroups tree: [root-inside-lxc@tst1 ~]# mount | grep cgroups cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on

On 06/10/2013 01:41 PM, pr.G wrote: > On Mon, Jun 10, 2013 at 09:29:32AM +0400, свящ. Георгий Гольцов wrote: >> On Mon, Jun 10, 2013 at 09:07:08AM +0800, Gao feng wrote: >>> On 06/09/2013 08:14 PM, pr.G wrote: >>>> Hello. >>>> >>>> Is it possible to start container via libvirt_lxc without mounting /sys >>>> inside container?

Hello The latest attempts that I made on fedora21 all gave me the same result I have tried . vanilla rpm from f21 (1.2.9 IIRC) . 1.2.14 . 1.2.13 . 1.2.12 these three ones I rebuilt from the source rpm published by libvirt eventually I reworked my own tools to enter the container via ssh, so this is not an immediate concern to me any longer but it is definitely odd I currently use 1.2.12

Hi there, Do you know if there is a way to modify how libvirt interacts with the cgroup? Because, I successfully add the /dev/net/tun support in my LXC container by doing: echo c 10:200 rwm >> /cgroup/libvirt/lxc/instance-00000005/devices.allow But when I restart the instance/LXC container, this option has gone. How can I make this persistant? Is there a configuration file? Thanks

Hi, I'm running OpenStack on CentOS 6.3 to manage lxc instances. And running into series of problem relating libvirt and lxc interaction. For example, libvirt_lxc segfault ( https://bugzilla.redhat.com/show_bug.cgi?id=874549) which has an upstream fix. And another bugs such as fail to start when SELinux disabled. Finally, I decides to adopt libvirt 0.10.2, self compiled from

Hello. Centos 7.6 with libvirt build from base "virt" repository: libvirt-daemon-driver-lxc-5.0.0-1.el7.x86_64 libvirt-client-5.0.0-1.el7.x86_64 libvirt-daemon-5.0.0-1.el7.x86_64 libvirt-daemon-driver-network-5.0.0-1.el7.x86_64 libvirt-libs-5.0.0-1.el7.x86_64 + systemd-219-62.el7_6.2.x86_64 Now lxc containers with type='direct' can be started, but can't be stopped :)

Hello, According to the docs, vcpupin will use either cgroups or sched_setaffinity to pin vcpu threads to cpus. How is this decision made? I observe differences even on different hosts featuring the same version of libvirtd (1.3.1): on one host vcpupin affects cpuset.cpus (cgroup), and on the other it affects vcpu threads affinity (observed through taskset). Thanks, Nikos -------------- next

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.

On Wed, Jan 15, 2014 at 05:49:23AM +0000, WANG Cheng D wrote: > Dear all > > I allocate only one vcpu for the container by the following > statement, that is, I want to pin the vcpu to physical core "2". > <vcpu placement='static' cpuset="2" >1</vcpu> > My host has 4 physical cores. Before test, all the 4 cores are > idle. After I run 4

Hi all, I'm new to LXC and libvirt. I have created a LXC container using libvirt. In domain XML file I have mentioned "memory" and "current memory" as 256 MB. Now I want to check the memory inside the container, but whenever I run top command or try to cat /proc/meminfo, it shows host machine's memory which is 3GB. So is there any command by which I can check

Hello. tl;dr = v1.0.0 can boot my LXC containers, v.1.0.1 and v.1.0.2 fails. Paraphrased error message: "lxcContainerMountProcFuse:616 : Failed to mount ..../meminfo" I'd like to know if my host is misconfigured, or my domains, or ... why 1.0.2 and 1.0.1 are not working for me. I've been using libvirt for a while to manage QEMU instances. I have experimented with lxc.

Dear list, I am bulding a VM using libvirt and lxc for linux container. I have an issue with my cgroups settings: gabx@hortensia ➤➤ ~ # virsh start dahlia error: Failed to start domain dahlia error: internal error: No valid cgroup for machine dahlia My environement: Host : Arch Linux - systemd 208-11, libvirt 1.2.1-4 guest : Arch Linux , machine name : dahlia , /etc/libvirt/lxc/dahlia.xml ,