virtualbox.org

Running VirtualBox 6.1 on Windows 10, with Guest Additions.
64-bit, 8GB on host, give 4GB to guest.

VirtualBox has been working perfectly for about a week, but today I started up my VM and encountered the Guru Meditation Error. Log attached.

Looking through the forums it seems the most common explanation has to do with VT-x being disabled, I don't think that's the issue but I am inexperienced.

Potentially relevant log lines?:
00:00:07.390493 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:07.612707 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000dd60000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0
00:00:07.615484 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:07.615529 Console: Machine state changed to 'GuruMeditation'

Thanks for the help.

Reducing VRAM from max (256) to 128 seems to have fixed it.

Hmm. I'm not convinced.

00:00:03.660393 Host RAM: 8117MB (7.9GB) total, 3581MB (3.4GB) available
...
00:00:03.821835 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:03.822089 VRamSize <integer> = 0x0000000010000000 (268 435 456, 256 MB)

As you can see, you started with about 3.6GB RAM available on your host, and then you assigned about 4.3GB to the VM. This is not a healthy scenario. Nibbling around the edges may seem to work for a while, but long term the fix is to add more RAM to the host, or substantially reduce RAM to the VM, e.g. reduce the RAM allocation to 2048MB. Leave the VRAM on 128MB until you can explain why this VM, with 3D acceleration disabled, needed more than say 64MB VRAM.

tgrosson wrote:VT-x being disabled, I don't think that's the issue

00:00:03.822350 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support

You are correct about VT-x, it is on and unimpeded.