Bug#1072831: getting memory info fails when running under lxc

2024-06-24 Thread Paul Slootman
On Mon 24 Jun 2024, Craig Small wrote: > On Sun, 9 Jun 2024 at 01:03, Paul Slootman wrote: > > I am running a number of virtual systems under lxc via libvirt. > > This means these systems share the host kernel (not like qemu where a > > whole virtual machine is emulated). > Hi Paul, > I did the

Bug#1072831: getting memory info fails when running under lxc

2024-06-23 Thread Craig Small
On Sun, 9 Jun 2024 at 01:03, Paul Slootman wrote: > I am running a number of virtual systems under lxc via libvirt. > This means these systems share the host kernel (not like qemu where a > whole virtual machine is emulated). Hi Paul, I did the following (as root) lxc-create --name debtest2 --t

Bug#1072831: getting memory info fails when running under lxc

2024-06-23 Thread Craig Small
Control: tags -1 fixed-upstream On Tue, 11 Jun 2024 at 21:16, Paul Slootman wrote: > I see I missed the case lseek() fails with another errno. > Updated patch attached. Thanks Paul, This was applied upstream at https://gitlab.com/procps-ng/procps/-/commit/104b3ce3df67092eeb868ba5e019cb895ebdf32

Bug#1072831: getting memory info fails when running under lxc

2024-06-12 Thread Jim Warner
On 6/12/24 9:35 AM, Jim Warner wrote: For what it's worth, I am unable to duplicate the meminfo problem in a newly created debian-bookworm based lxc container. I'm using the snap version of lxd identified as:     $ lxc --version     5.21.1 LTS The top, ps and free programs (all identified as

Bug#1072831: getting memory info fails when running under lxc

2024-06-12 Thread Jim Warner
Hi Guys, For what it's worth, I am unable to duplicate the meminfo problem in a newly created debian-bookworm based lxc container. I'm using the snap version of lxd identified as: $ lxc --version 5.21.1 LTS The top, ps and free programs (all identified as from procps-ng 4.0.2) work j

Bug#1072831: getting memory info fails when running under lxc

2024-06-11 Thread Paul Slootman
On Tue 11 Jun 2024, Paul Slootman wrote: > This works for me. Patch attached. I see I missed the case lseek() fails with another errno. Updated patch attached. Paul --- library/meminfo.c.orig 2023-07-11 11:09:18.436786212 +0200 +++ library/meminfo.c 2024-06-11 13:11:12.878627527 +0200 @@ -646,1

Bug#1072831: getting memory info fails when running under lxc

2024-06-11 Thread Paul Slootman
tags 1072831 patch thanks On Tue 11 Jun 2024, Craig Small wrote: > Could you check to see if in the container that lxcfs has overwritten > the /proc/meminfo file? They sometimes do this for /proc/uptime. They > might have messed one of the lines up and choked procps; I'm thinking > like a tab/spa

Bug#1072831: getting memory info fails when running under lxc

2024-06-10 Thread Craig Small
On Sun, 9 Jun 2024 at 01:03, Paul Slootman wrote: > # free > free: Unable to create meminfo structure That's procps_meminfo_new() failing but /proc/meminfo exists. The function: checks the parameters allocates some memory for the structure runs meminfo_make_hash_failed(), which sets up the h

Bug#1072831: getting memory info fails when running under lxc

2024-06-08 Thread Paul Slootman
Package: procps Version: 2:4.0.2-3 Severity: normal I am running a number of virtual systems under lxc via libvirt. This means these systems share the host kernel (not like qemu where a whole virtual machine is emulated). I upgraded one to bookworm today, and when running 'ps faxu' or 'free' I ge