Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Discussions related to using VirtualBox on Linux hosts.
Post Reply
hottobar
Posts: 28
Joined: 4. Feb 2021, 11:56

Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by hottobar »

Hi,

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've tried with Linux version 5.8.0-41 and 5.9.16, VirtualBox versions 6.1.16 (Ubuntu's repo) and 6.1.18 r142142 (Oracle's repo).
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
Same VM on Intel i5-1135G7 but converted to QEMU/KVM is 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

.
Attachments
VBox.log_STATUS_DATATYPE_MISALIGNMENT.zip
(32.55 KiB) Downloaded 38 times
Last edited by hottobar on 20. May 2021, 18:11, edited 3 times in total.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by mpack »

This doesn't look like a VirtualBox error. The guest OS has the error, it uses the Hyper-v API to report the error to VirtualBox, which reports the error to you.
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
I'm going to assume that the source is some third party guest driver or AV. Nothing that comes as standard with Windows.
hottobar
Posts: 28
Joined: 4. Feb 2021, 11:56

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by hottobar »

This is a fresh install from Microsoft's ISO, no third party AV installed, only VirtualBox Guest Additions (version 6.1.18).

I can try disinstalling the guest additions if that makes sense.
ahorton
Posts: 1
Joined: 5. Feb 2021, 05:10

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by ahorton »

I've been getting the exact same problem (and STATUS_DATATYPE_MISALIGNMENT error messages) with Windows 10 guests on an Ubuntu hosts for some time. The VM reboots at random intervals of a few minutes to a few 10's of minutes. This happens with either Ubuntu 20.04 LTS and Ubuntu 20.10, and with the versions of VirtualBox from both Ubuntu's and Oracle's repos. System is a Core i7-1065G7 based laptop (Dell XPS 13 7390 2-in-1). Currently I have a Ubuntu 20.10 host, with Ubuntu's 5.8.0-41 kernel and VirtualBox 6.1.18 r142142 from the Oracle repos.

In order to eliminate the possibility that it was a problem within the specific VM I'm running I have been trying to create a new VM and install a fresh copy of Windows 10 from the latest ISO, but the Windows installer always ends up crashing with the same STATUS_DATATYPE_MISALIGNMENT error before the installation can complete. Attached is an example log from one of these failed attempts to install Windows 10.
Attachments
Windows10-2021-02-05-15-35-09.log.zip
Log from failed Windows install attempt
(25.25 KiB) Downloaded 25 times
hottobar
Posts: 28
Joined: 4. Feb 2021, 11:56

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by hottobar »

I've tried uninstalling the Guest Additions but the VM still reboots.

For the next step I'll try to use this same Win 10 20H2 VM with QEMU.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by fth0 »

ahorton wrote:Ubuntu's 5.8.0-41 kernel
In all similar cases that I saw in the previous weeks months, the Linux kernel 5.8 was also a prerequisite. One user started with Ubuntu 20.04 and the stock kernel 5.4, and after they switched to kernel 5.8 the crashes began.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by fth0 »

In another thread about this type of crash, I've posted Re: Windows 10 guest on 5.8 kernel STATUS_DATATYPE_MISALIGNMENT exception, suggesting further experiments. If you like, you can try one or more of them to let us possibly narrow down the problem a bit more.
hottobar
Posts: 28
Joined: 4. Feb 2021, 11:56

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by hottobar »

fth0 wrote:In another thread about this type of crash, I've posted Re: Windows 10 guest on 5.8 kernel STATUS_DATATYPE_MISALIGNMENT exception, suggesting further experiments. If you like, you can try one or more of them to let us possibly narrow down the problem a bit more.
A. Start the VM with Windows in Safe Mode and wait up to 1 hour. Does the crash occur?
In safe mode the VM didn't reboot in 1.5 hours of testing.
B. In the VM configuration, disable System > Acceleration > Nested Paging. Start the VM and wait up to 1 hour (note that without nested paging, a VM can be up to 10 times slower). Does the crash occur?
With this configuration the VM was unable to boot. It got stuck on a black screen (no windows logo) but with the spinning circles. After a while it auto rebooted and tried to start the boot recovery GUI but then got stuck with a black screen.
C. In the VM configuration, set System > Processor > Processor(s) to 1 CPU, and disable System > Motherboard > I/O APIC. Start the VM from a Windows 10 ISO and wait up to 1 hour. Does the crash occur?
With this configuration the Win 10 ISO is unable to boot. It immediately shows the screen you see in the attachment (tried with different graphics card options).
Attachments
VirtualBox_Win 10 test_06_02_2021_15_06_45.png
VirtualBox_Win 10 test_06_02_2021_15_06_45.png (5.08 KiB) Viewed 25768 times
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by fth0 »

Thanks for trying. Can you provide zipped VBox.log files for B and C?
hottobar
Posts: 28
Joined: 4. Feb 2021, 11:56

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by hottobar »

fth0 wrote:Thanks for trying. Can you provide zipped VBox.log files for B and C?
Here are the two log files.

Test B is: boot from disk -> spinning circles -> auto reboot -> spinning circles -> auto reboot -> hang on black screen (recovery mode) -> manual power off

Test C is: boot from ISO -> appearance of the Windows logo for a very brief moment -> garbled screen -> manual power off
Attachments
Tests_B_and_C_Logs.zip
(59.05 KiB) Downloaded 24 times
hottobar
Posts: 28
Joined: 4. Feb 2021, 11:56

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by hottobar »

I copied the VM (same configuration) to a different host system and it worked with no problems for more than an hour.

VirtualBox is the same version: 6.1.18 r142142 (Oracle's repo)

The new host's OS is Ubuntu 20.04 with Linux 5.8.18 and an AMD Ryzen 9 3900X.
Attachments
VBox.log.zip
(27.02 KiB) Downloaded 19 times
hottobar
Posts: 28
Joined: 4. Feb 2021, 11:56

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by hottobar »

Looking at other people's posts with the same problems, I'm starting to think it may be CPU related.

This post:
HP ProBook 650 G8 Intel, 11th gen (Tiger Lake): crash (code 0xffffffff80000002)
DIY system, AMD Zen 2: works

viewtopic.php?f=7&t=101280
Dell XPS 13 (2016), Intel 7th gen (Kaby Lake): works
Dell XPS 13 (2020), Intel 10th gen (Ice Lake): crash (code 0xffffffff80000002)

viewtopic.php?f=7&t=101353
Dell XPS 13 9300, Intel 10th gen (Ice Lake): crash (code 0xffffffff80000002)

viewtopic.php?f=7&t=99789
Dell Inspiron 5593, Intel 10th gen (Ice Lake): crash (code 0xffffffff80000002)
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by fth0 »

Without reading your latest posting beforehand, I came to a similar conclusion:

One of the Intel CPUs "i7-1065G7", "i5-1135G7" and "i7-1185G7" was used in all cases, and VirtualBox didn't seem to understand several new CPUID bits. Additionally, your VBox_test_B.log contains some log messages I've never seen before. They document unexpected or unhandled Page Fault events (PF).

Can you try if forcing a CPU profile eliminates the crash and could be used as a workaround?

Code: Select all

VBoxManage modifyvm "<VM name>" --cpu-profile "Intel Core i7-6700K"
If the crash still happens, post another zipped VBox.log file, please. You can later undo the setting with

Code: Select all

VBoxManage modifyvm "<VM name>" --cpu-profile "host"
hottobar
Posts: 28
Joined: 4. Feb 2021, 11:56

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by hottobar »

fth0 wrote:Can you try if forcing a CPU profile eliminates the crash and could be used as a workaround?
Nice try, but no cigar. :(
The VM crashed with the same exception code. :?
Attachments
VBox_i7-6700K_profile.log.zip
(30.59 KiB) Downloaded 28 times
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Ubuntu 20.04 host, Win 10 guest constant reboot (STATUS_DATATYPE_MISALIGNMENT)

Post by fth0 »

Bummer! :( Anyway, thanks for trying. :)

I'm out of ideas for the moment. IMHO, the next step would call for Windows kernel debugging, but I'm not savvy enough for that (yet). I'll post my current state of knowledge to the Bugtracker (possibly in #20165), either tonight or tomorrow, and then we'll have to wait if or when we'll get any reaction from the VirtualBox developers.
Post Reply