I see similar numbers:
angel@lucifer:~$ sysctl hw | grep memI always took for granted that
hw.physmem=8453619712
hw.usermem=8453464064
angel@lucifer:~$ top | grep Memory
Memory: Real: 98M/4030M act/tot Free: 3779M Cache: 3116M Swap: 0K/4088K
top output was to be interpreted as 'Real:' + 'Free:' = total memory, but now I'm deep in a sea of doubt 😕
...
@angel @Hetzner_Online Can you use procmap on your VM? I get permission denied on all processes as root.
@angel @solene Any idea how to debug this? To find the cause for that issue.
...
Sorry, I forgot to mention in my previous message that the output I copypasted was not from a VM, but from a real computer under my desk.
In this very same machine, I get the error
procmap: /dev/mem: Operation not permittedno matter the option I give to
procmap. I vaguely recall this command working in the past....
@angel Thank you for that clarification. Wonder what the issue is here ...
That narrows it down to either some type of BIOS/UEFI memory setting or a bug on OpenBSD. 🤔
It's the first time that this happens to me with my first 7.2 installation.
procmap seems to be an indicator for that bug.
Edit: I was wrong about procmap. https://marc.info/?l=openbsd-cvs&m=147481705211536&w=2
You're right I think. I have no idea why tot and free are split though. 🤔
I usually use free¹ (totals) which shows the correct amount of "physical memory available", but not the correct "used amount" anymore. 🙄
The values in top work if you accumulate the values tot + free = total RAM - shared video memory (if used). I couldn't find a better explanation either².
¹ https://github.com/NanXiao/free
² https://marc.info/?t=161031536400002&r=1&w=2 https://marc.info/?l=openbsd-misc&m=160531375702042&w=2
