Linux VM aborts randomly on MacOS 10.15.6 Host

[mlemnian]

Hello together,

recently I switched from a Windows Host machine to a Macbook Pro 16".
For my backend development, I'm using a VirtualBox Linux VM based on CentOS 7.

Currently, I'm facing random crashes (abortions) of my dev-env-VM.
It seems that the crashes occur every time away from the keyboard (the screensaver is active) or I'm clicking on an application in the host system.
I attached the VB logs and the MacOS console log.

I configured the following stuff for the VM:
* disabled the audio for the guest VM (see Screenshot 2020-09-20 at 16.07.28.png)
* disabled 3d acceleration
* disabled the Remote Display
* 6 Cores
* 9GiB RAM
* Enabled PAE/NX
* Paravirtualization Interface: default and enabled "Nested Paging"

I explicitly configured the following Security Settings for VirtualBox within MacOS:
* granted Full Disk Access
* revoked Input Monitoring (I also disabled the "Auto Capture Keyboard" setting in VB preferences)

[scottgus1]

The only thing I see is that you have all six physical cores available for the guest to use. Try to achieve stable running on two cores, then increase. The host needs something to run on, too.

[mlemnian]

The only thing I see is that you have all six physical cores available for the guest to use. Try to achieve stable running on two cores, then increase. The host needs something to run on, too.

I decreased the number of cores to 3, otherwise, all the programs (IDE, several docker containers, application server, browser, ...) inside the VM are unusable, but still the same issue:
After some time the VM just aborts.

ps: the VM was created via vagrant and is based on a centos vagrantbox. I have the impression, that the VM is more unstable when I use "vagrant up" rather than the VirtualBox Manager.

[granada29]

@mlemnian

Have you installed the supplemental update to 10.15.6 ? Without the update there is a major kernel memory leak and I wonder if that may be the cause of your problem

[mlemnian]

@mlemnian

Have you installed the supplemental update to 10.15.6 ? Without the update there is a major kernel memory leak and I wonder if that may be the cause of your problem

@granada29
I did the supplemental update because I had huge issues with VirtualBox and VMware.

[mlemnian]

Hello together,

today I updated to macOS 10.15.7, but the issue is still present.