I'm having constant reboots with a Windows 10 20H2 VM, usually after a few minutes of uptime.
If I switch the paravirtualization interface to Legacy it lasts a bit longer (maybe 30').
This is the part of the log with the exception:
Code: Select all
00:04:04.476177 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffff80000002 P2=0xfffff80426ae4793 P3=0xffffbd0cd2c0237a P4=0x7010008004002001
00:04:04.476246 GIMHv: BugCheck 1e {ffffffff80000002, fffff80426ae4793, ffffbd0cd2c0237a, 7010008004002001}
00:04:04.476246 KMODE_EXCEPTION_NOT_HANDLED
00:04:04.476246 P1: ffffffff80000002 - exception code - STATUS_DATATYPE_MISALIGNMENT
00:04:04.476246 P2: fffff80426ae4793 - EIP/RIP
00:04:04.476247 P3: ffffbd0cd2c0237a - Xcpt param #0
00:04:04.476247 P4: 7010008004002001 - Xcpt param #1
I would also try Linux 5.10 but VirtualBox's dkms driver won't compile with that kernel version.
My system is an HP ProBook 650 G8 with an Intel i5-1135G7 (Tiger Lake) CPU.
My next step to solve the problem would be converting all my VMs to qemu, but I'd rather not...
EDIT 27/04/2021: an update on the current state of the problem:
I've tested the same VM (Win10 20H2 64bit), no Guest additions nor 3rd party software, on VirtualBox 6.1.16, 6.1.18, 6.1.20, Kernel 5.8, 5.9, 5.10 with these results:
- Intel i5-1135G7 (Tiger Lake): STATUS_DATATYPE_MISALIGNMENT
- AMD Ryzen 3900X (Zen 2): stable
A ticket has been opened: https://www.virtualbox.org/ticket/20180
EDIT 20/05/2021: a possible workaround has been found (thanks fth0!):
boot your host OS with the Linux Kernel parameter split_lock_detect=off
.