[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
me
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,
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 wrote:
On 01/30/2014 10:11 AM, mallu mallu wrote:
> I'm trying to permanently change
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//. This didn't help. It appears that
> libvirt is not reading changes in cgroup.
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//. This didn't help. It appears that
libvirt is not reading changes in cgroup.
My requirements are
1) Be able to dynamically c
