You are not logged in.
I'm unable to start any VirtualBox machine, and receiving the error VERR_NO_LOW_MEMORY, however this is a workstation with 96GB of RAM and with only 20GB in use at the moment.
Any ideas what could be going on? Just upgraded to Linux kernel 6.10.0, so may it be related? vboxdrv module and dependencies are loaded fine.
Last edited by roviq (2024-07-26 00:40:48)
Offline
Hmm, wait a minute, noticed with 'free' command that buff/cache is filled up with 70GB, so there are less than 1GB of RAM "really-available" in this system, after forcing a "purge" with:
echo 3 > /proc/sys/vm/drop_cachesNow VirtualBox is working again... this shouldn't have happened, does kernel 6.10.0 has a new memory/page allocator that doesn't make up space for continuous RAM allocation?
Should I tag this as [SOLVED]? Or is there an issue with memory allocation? First time I experience this with VirtualBox and Linux, usually my RAM is fully used in terms of buff/cache, so this wasn't an issue before.
Last edited by roviq (2024-07-26 00:40:35)
Offline
I had this issue this morning too with 30Gb of free memory.
Updating linux to 6.10.1 and virtualbox-host-modules-arch to 7.0.20-5 the issue has gone. I have no more info about that issue.
Offline
Hmm, wait a minute, noticed with 'free' command that buff/cache is filled up with 70GB, so there are less than 1GB of RAM "really-available" in this system, after forcing a "purge" with:
echo 3 > /proc/sys/vm/drop_cachesNow VirtualBox is working again... this shouldn't have happened, does kernel 6.10.0 has a new memory/page allocator that doesn't make up space for continuous RAM allocation?
Should I tag this as [SOLVED]? Or is there an issue with memory allocation? First time I experience this with VirtualBox and Linux, usually my RAM is fully used in terms of buff/cache, so this wasn't an issue before.
Thanks! I had the same issue today with VirtualBox 7.0.20 r163906 and 6.10.3. - the 'available' amount from 'free' was low despite this machine actually having 28Gb free and the VM memory set to 8Gb. Forcing the purge fixed the issue.
Offline
I'm still getting this with Linux 6.10.6 and virtualbox host mods 7.0.20-13 - all up to date. I appreciate the workaround (getting tired of rebooting), but there's an underlying problem here that's not getting fixed.
Can anyone provide some update on if or whether this is being fixed, and maybe a when?
Offline
I am also having this problem with multiple Arch natives, most of which have 32 Gb physical memory and one of which has 64 Gb physical memory. All VMs have less that 1/2 of the physical memory allocated to the VM; (in one case less than 1/8th).
Over several years I have not seen this behavior before.
I am investigating the problem now on one of these machines and, in fact, when the Vbox memory fault occurred the free memory was low and the cached memory was high.
Offline
Current issue. Linux 6.10.10, VirtualBox 7.1.2-1 (7.1.2r164945). `free -h` reports 23Gi of ram, 8.2Gi available, 239Mi free. VM configured to use 9941 MB. `echo 3 > /proc/sys/vm/drop_caches` worked for me.
Offline
I can confirm that I stumbled on the same issue.
Linux 6.11.5-zen1-1-zen
Virtualbox 7.1.4 r165100
Every time I had the issue, it was after cloning a VM with a disk (vdi) of 50+ GB.
echo 3 > /proc/sys/vm/drop_cachesworked!
Offline
I was having this error on a cloned machine, which was in bridge mode, I just clicked to define another mac
right click on the machine > configuration > network > mac address option "↺"
Offline