That particular error was resolved, but the lxc live migration doesn't work
for a different reason now. We now get an error that says "can't dump ghost
file" because of apparent size limitations - a limit less than the size of
any lxc container we have running here.
(In contrast, live migration on
Dear Harald,
years ago I scripted my own lxc-free to be used as something lxc-aware inside
the container. It's based on the memory controllers values, too. Please take a
look at memory.stats, too. Here, I get other values to calculate the values for
RSS+Cache, active, free and used RAM, too.
Hi folks,
Is there some way to monitor local memory swapping *inside*
the container?
Long story:
I had to restrict memory usage for a set of containers, using
lines like
lxc.cgroup.memory.limit_in_bytes = 12G
in the config file. The memory limits are not the same for
all hosts.
Of cour
> On Tue, Mar 29, 2016 at 09:30:19AM -0700, jjs - mainphrame wrote:
> > On Tue, Mar 29, 2016 at 7:18 AM, Tycho Andersen <
> > tycho.andersen at canonical.com> wrote:
> >
> > > On Mon, Mar 28, 2016 at 08:47:24PM -0700, jjs - mainphrame wrote:
> >> > I've looked at ct migration between 2 ubuntu 16
