Opened 8 months ago
Last modified 8 months ago
#22102 new defect
If a guest OS is assigned more than 32 GB of RAM, it uses disk
| Reported by: | f00dl3 | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox-7.0.18 |
| Keywords: | RAM | Cc: | |
| Guest type: | Linux | Host type: | Linux |
Description
When a guest OS is assigned greater than 32 GB of RAM, it appears to thrash the disk maxing out the IO reads (502 MB/sec on a SSD.)
You can reproduce this bug by assigning 64 GB of RAM on a system with 128 GB of RAM. Once the RAM use inside the VM breaks 32 GB, it starts showing excessive disk reads/writes on iotop, which makes the virtual machine completely inaccessible and unresponsive, and OOM killer kills all processes active on the VM while this thrashing is occurring.
Note:
See TracTickets
for help on using tickets.
Problem actually still exists. Updated Linux kernel to 6.5 and that has not resolved the issue. Reducing RAM to 32 GB has provided a workaround for the moment, but would like to be able to assign more as this is the only reason I bought 128 GB of RAM.
The kernel upgrade has removed the excessive disk read/writes, but the guest OS "VDI" disk read/writes is limited to 0-50 kb/sec, even without any IO activity.