similar to: Dynamically setting permanent memory libvirt-lxc

Eric, thank you for your response. Virsh memtune, setmaxmem and setmem won't survive a reboot. I'm hoping to find  a solution that can survive reboot.   On Thursday, January 30, 2014 11:36 AM, Eric Blake <eblake@redhat.com> wrote: On 01/30/2014 10:11 AM, mallu mallu wrote: > I'm trying to permanently change memory allocation for a libvirt-lxc domain. So far I tried

[please don't top-post on technical lists; also, it would be nice if you could convince your mailer to wrap long lines) > Eric, thank you for your response. Virsh memtune, setmaxmem and setmem won't survive a reboot. Ah, but they DO survive reboots, if you use the right options.  'virsh memtune --live --config' affects both the running guest and the next boot. -------

Hi all I have CentOS Linux release 7.0.1406, libvirt 1.2.7 installed. Just after create and start inside LXC container present cgroups. Example for memory: [root@ce7-t1 /]# ls -la /sys/fs/cgroup/memory/ total 0 drwxr-xr-x 2 root root 0 Sep 15 17:14 . drwxr-xr-x 12 root root 280 Sep 15 17:14 .. -rw-r--r-- 1 root root 0 Sep 15 17:14 cgroup.clone_children --w--w--w- 1 root root 0 Sep 15

On 01/30/2014 10:11 AM, mallu mallu wrote: > I'm trying to permanently change memory allocation for a libvirt-lxc domain. So far I tried changing memory in memory.limit_in_bytes under /cgroup/memory/libvirt/lxc/<container>/. This didn't help. It appears that libvirt is not reading changes in cgroup. > > My requirements are > > 1) Be able to dynamically change

On 01/30/2014 01:26 PM, mallu mallu wrote: [please don't top-post on technical lists; also, it would be nice if you could convince your mailer to wrap long lines) > Eric, thank you for your response. Virsh memtune, setmaxmem and setmem won't survive a reboot. Ah, but they DO survive reboots, if you use the right options. 'virsh memtune --live --config' affects both the

hi, I am currently investigating a bug with libvirt lxc. Whenever I do a systemctl daemon-reload on the host, my container loses his memory limit and then reports having access to 8 exabyte of memory. I have tracked the issue down to two parts: memory.limit_in_bytes jumps from the correct value to 9223372036854771712. libvirt lxc appears to set the memory limit in transient way without writing

hello, i am new to lxc, i have created a lxc container on fedora 19 i created a container rootfs of fedora 19 by using yum --installroot=/containers/test1 --releasever=19 install openssh test1.xml file for container test1 <domain type="lxc"> <name>test1</name> <vcpu placement="static">1</vcpu> <cputune>

On Thu, Aug 8, 2013 at 9:39 AM, Martin Kletzander <mkletzan@redhat.com> wrote: > At first let me explain that libvirt is not ignoring the cache=none. > This is propagated to qemu as a parameter for it's disk. From qemu's > POV (anyone feel free to correct me if I'm mistaken) this means the file > is opened with O_DIRECT flag; and from the open(2) manual, the O_DIRECT

Hello, iam currently trying to run LXC Containers with libvirt but the memory limit doesn't want to work in the container i see the full 32GB from the Host OS iam pretty sure that iam missing a configline in the xml lxc-template ~ # free -m total used free shared buff/cache available Mem: 32108 626 31396 249 85

Can someone tell me how I can upgrade OS on a lxc container? I want to upgrade my containers from centos 6.4 to centos 6.5. I have upgraded the host on which these containers are running on to centos. But want to know how to upgrade the containers. Thank you

Has anyone seen this issue? We're running containers under CentOS 7.2 and some of these containers are reporting incorrect memory allocation in /proc/meminfo. The output below comes from a system with 32G of memory and 84GB of swap. The values reported are completely wrong. # cat /proc/meminfo MemTotal: 9007199254740991 kB MemFree: 9007199224543267 kB MemAvailable: 12985680

Hi All, I am new to libvirt, i wander how we can achieve below objective, i read through a lot from libvirt.org but couldn't found any thing solid something equivalent to this:- virsh dumpxml dom > /tmp/dom.xml $EDITOR /tmp/dom.xml && virsh define /tmp/dom.xml What i try to achieve is to have one management server that install with libvirt in place then we can use libvirt

Hi all. I use LXC on Centos 7 x86-64, with libvirt version 1.2.6 and 1.2.12 My container has bridged network: # virsh dumpxml test1 <domain type='lxc'> <name>test1</name> <uuid>518539ab-7491-45ab-bb1d-3d7f11bfb0b1</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory>

I upgraded my container from CentOS 6.4 to CentOS 6.5. Everything looks good after upgrade until reboot. When rebooted to container I'm getting the following errors.. Any help would be greatly appreciated /bin/mknod: `/dev/lp2': Operation not permitted /bin/chown: cannot access `/dev/lp2': No such file or directory /bin/mknod: `/dev/lp3': Operation not permitted /bin/chown: cannot

Hi Currently we are using cgroups to limit samba memory usage on our target we have limited the memory to 20MB and we are able to see samba is restricted to it. With this we are able to restrict the cache memory to ~34MB (never goes beyond this) BUt issue we arere facing is the Buffers are increasing gradually and it is not able to restrict. Commands Used to restrict memory on target: echo

Hi all > Has anyone seen this issue? We're running containers under CentOS 7.2 > and some of these containers are reporting incorrect memory allocation > in /proc/meminfo. The output below comes from a system with 32G of > memory and 84GB of swap. The values reported are completely wrong. yes, it's occured time to time on our installations. Centos 7.2 + libvirt 1.2.18 and

On 08/08/2013 05:03 PM, Brano Zarnovican wrote: > On Thu, Aug 8, 2013 at 9:39 AM, Martin Kletzander <mkletzan@redhat.com> wrote: >> At first let me explain that libvirt is not ignoring the cache=none. >> This is propagated to qemu as a parameter for it's disk. From qemu's >> POV (anyone feel free to correct me if I'm mistaken) this means the file >> is

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

On Mon, Mar 03, 2014 at 03:52:01PM +0100, Dariusz Michaluk wrote: > Hi. > > Another week, another experiment ;) I was trying to run systemd user > session for non-root user, for example darek (uid=1000), operation > failed with error: > > systemd[26]: pam_unix(systemd-user:session): session opened for user > darek by (uid=0) > systemd[1]: Started Login Service. >

Howdy, I am playing around with asterisk within an LXC container on Ubuntu 11.04. I have asterisk (1.4.42) running fine, but want access to dahdi_dummy for timing (meetme). I have dahdi installed on the "host", and dahdi_dummy is loaded: root at astnorth:/# ls -ltr /dev/dahdi total 0 crw-rw---- 1 root root 196, 250 2011-06-08 13:59 transcode crw-rw---- 1 root root 196, 253