On Mon, 29 Mar 2021 07:49:24 +0200 Maximilian Philipps
wrote:
hi Michael,
I currently can't test that. Given that bullseye isn't released yet, I
don't have a test environment here.
When bullseye is released I will try to test it again, for time being I
have moved all libvirt-lxc container
hi Michael,
I currently can't test that. Given that bullseye isn't released yet, I
don't have a test environment here.
When bullseye is released I will try to test it again, for time being I
have moved all libvirt-lxc container to use lxc.
Regards,
Maximilian Philipps
Hi Maximilian,
can you please check, if you can still reproduce the issue on bullseye,
where cgroupv2, i.e. unified, is the default cgroup hierarchy.
Regards,
Michael
Am 25.10.2019 um 16:35 schrieb Maximilian Philipps:
hi
I can now reliably trigger the 8 exabyte issue. When I start a
hi
I can now reliably trigger the 8 exabyte issue. When I start a
libvirt-lxc container, libvirts sets the memory limit.
This can be seen with:
cat
/sys/fs/cgroup/memory/machine.slice/machine-lxc\x2d27166\x2dhost.domain.tld.scope/memory.limit_in_bytes
2147483648
If I now call systemctl
hi,
After digging a bit more, it appears that after the update from stretch
to buster we are using some mix cgroupv1 and cgroupv2.
/sys/fs/cgroup/ is still a tmpfs and /sys/fs/cgroup/unified/ exits, but
hast no controllers. So apparently systemd should still use the
controllers from v1 with the
Recently updated one of the hosts and the containers running on it from
stretch to buster.
With buster's 241-7~deb10u1 the issue still exists. I have tried working
around this issue by setting a memory limit on the -.slice from within
the container, but this is fairly unreliable.
Would you mind testing with systemd v239 from unstable/testing and
eventually raise this upstream at https://github.com/systemd/systemd
tbh, I'm not sure what the expected behaviour is in that regard and if
this maybe just a configuration issue.
--
Why is it that all of the instruments seeking
On 02/19/2018 02:07 PM, Maximilian Philipps wrote:
On 02/19/2018 01:50 PM, Michael Biebl wrote:
Am 19.02.2018 um 13:09 schrieb Maximilian Philipps:
Package: systemd
Version: 232-25+deb9u1
Severity: important
Hi
I have an issue with Systemd unsetting the memory limit for my
container,
On 02/19/2018 01:50 PM, Michael Biebl wrote:
Am 19.02.2018 um 13:09 schrieb Maximilian Philipps:
Package: systemd
Version: 232-25+deb9u1
Severity: important
Hi
I have an issue with Systemd unsetting the memory limit for my container,
whereupon programs like free and htop report having
Am 19.02.2018 um 13:09 schrieb Maximilian Philipps:
> Package: systemd
> Version: 232-25+deb9u1
> Severity: important
>
> Hi
>
> I have an issue with Systemd unsetting the memory limit for my container,
> whereupon programs like free and htop report having access to 8 exabyte
> of memory.
>
>
Package: systemd
Version: 232-25+deb9u1
Severity: important
Hi
I have an issue with Systemd unsetting the memory limit for my container,
whereupon programs like free and htop report having access to 8 exabyte
of memory.
The setup is the following:
Host:
Release: Debian jessie
Kernel:
11 matches
Mail list logo
