On Fri, 2023-06-09 at 17:16 +0200, Anael Mobilia wrote:
[...]
> During the launch of the partition (before the installer provide the
> choice on how did I want to partition manually, automatically, ...),
> OOM-killer is called, stopping the installation
> 
> Syslog :
> Jun  9 14:50:43 syslogd started: BusyBox v1.36.1
> Jun  9 14:50:43 kernel: klogd started: BusyBox v1.36.1 (Debian 1:1.36.1-1)
> Jun  9 14:50:43 kernel: [    0.000000] Linux version 6.1.0-9-amd64 
> (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld 
> (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 
> (2023-05-08)
> Jun  9 14:50:43 kernel: [    0.000000] Command line: 
> BOOT_IMAGE=/install.amd/vmlinuz priority=low vga=788 
> initrd=/install.amd/initrd.gz ---
> Jun  9 14:50:43 kernel: [    0.000000] x86/fpu: x87 FPU will use FXSAVE
> Jun  9 14:50:43 kernel: [    0.000000] signal: max sigframe size: 1440
> Jun  9 14:50:43 kernel: [    0.000000] BIOS-provided physical RAM map:
> Jun  9 14:50:43 kernel: [    0.000000] BIOS-e820: [mem 
> 0x0000000000000000-0x000000000009fbff] usable
> Jun  9 14:50:43 kernel: [    0.000000] BIOS-e820: [mem 
> 0x000000000009fc00-0x000000000009ffff] reserved
> Jun  9 14:50:43 kernel: [    0.000000] BIOS-e820: [mem 
> 0x00000000000f0000-0x00000000000fffff] reserved
> Jun  9 14:50:43 kernel: [    0.000000] BIOS-e820: [mem 
> 0x0000000000100000-0x000000003ffc9fff] usable
> Jun  9 14:50:43 kernel: [    0.000000] BIOS-e820: [mem 
> 0x000000003ffca000-0x000000003fffffff] reserved
> Jun  9 14:50:43 kernel: [    0.000000] BIOS-e820: [mem 
> 0x00000000feffc000-0x00000000feffffff] reserved
> Jun  9 14:50:43 kernel: [    0.000000] BIOS-e820: [mem 
> 0x00000000fffc0000-0x00000000ffffffff] reserved

That's 1 GiB RAM, not 32 GiB.  Still, that should be more than enough
for installation.

[...]
> Jun  9 14:55:00 kernel: [  260.262259] active_anon:35811 inactive_anon:26906 
> isolated_anon:0
> Jun  9 14:55:00 kernel: [  260.262259]  active_file:0 inactive_file:0 
> isolated_file:0
> Jun  9 14:55:00 kernel: [  260.262259]  unevictable:0 dirty:0 writeback:0
> Jun  9 14:55:00 kernel: [  260.262259]  slab_reclaimable:4417 
> slab_unreclaimable:7292
> Jun  9 14:55:00 kernel: [  260.262259]  mapped:2481 shmem:54494 pagetables:198
> Jun  9 14:55:00 kernel: [  260.262259]  sec_pagetables:0 bounce:0
> Jun  9 14:55:00 kernel: [  260.262259]  kernel_misc_reclaimable:0
> Jun  9 14:55:00 kernel: [  260.262259]  free:11279 free_pcp:2112 free_cma:0
> Jun  9 14:55:00 kernel: [  260.262273] Node 0 active_anon:53632kB 
> inactive_anon:60236kB active_file:0kB inactive_file:0kB unevictable:0kB 
> isolated(anon):0kB isolated(file):0kB mapped:9860kB dirty:0kB writeback:0kB 
> shmem:90728kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 14336kB 
> writeback_tmp:0kB kernel_stack:2032kB pagetables:620kB sec_pagetables:0kB 
> all_unreclaimable? yes
> Jun  9 14:55:00 kernel: [  260.262283] Node 1 active_anon:89612kB 
> inactive_anon:47388kB active_file:0kB inactive_file:0kB unevictable:0kB 
> isolated(anon):0kB isolated(file):0kB mapped:64kB dirty:0kB writeback:0kB 
> shmem:127248kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 4096kB 
> writeback_tmp:0kB kernel_stack:392kB pagetables:172kB sec_pagetables:0kB 
> all_unreclaimable? yes
[...]

So that's approximately:

 46 MiB of slab (kernel heap)
213 MiB of shmem (mostly initramfs files)
263 MiB of anon (process heap and stack)
 13 MiB of other stuff
-------
536 MiB

which is well under 1 GiB.  It seems like there must be a lot of kernel
memory allocations that aren't being accounted here, and might have
been leaked.

But you will probably succeed in installing if you correct the memory
allocation for this VM to the intended 32 GiB.

Ben.

-- 
Ben Hutchings
Theory and practice are closer in theory than in practice - John Levine

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to