search for: mallu

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 memory of a LXC domain without reboot 2) The memory change must survive

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 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. > >...

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. > >...

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 o...

[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. -------

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

On Fri, Nov 14, 2014 at 07:32:46PM +0000, mallu mallu wrote: > 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...

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

...ess sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc [6] My problem is i have installed '4' virtual machines. each virtual machine have 256Mb RAM. But i am not able to run 4 virtual machines at a time. Please help me, what should i have to do? Thanks mallu -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20080913/accf6da0/attachment-0002.html>