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

Discussions related to using VirtualBox on Linux hosts.

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

Postby hottobar » 27. Apr 2021, 12:59

Tested the same VM Windows 10 20H2 64-bit on the same Tiger Lake system, with the latest VirtualBox 6.1.20 r143896 (Oracle's repo) and still getting STATUS_DATATYPE_MISALIGNMENT exception.
Code: Select all   Expand viewCollapse view
00:30:18.095230 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffff80000002 P2=0xfffff80582ce4793 P3=0xffffba80840362fc P4=0x7010008004002001
00:30:18.095305 GIMHv: BugCheck 1e {ffffffff80000002, fffff80582ce4793, ffffba80840362fc, 7010008004002001}
00:30:18.095306 KMODE_EXCEPTION_NOT_HANDLED
00:30:18.095306 P1: ffffffff80000002 - exception code - STATUS_DATATYPE_MISALIGNMENT
00:30:18.095306 P2: fffff80582ce4793 - EIP/RIP
00:30:18.095306 P3: ffffba80840362fc - Xcpt param #0
00:30:18.095306 P4: 7010008004002001 - Xcpt param #1
Attachments
VBox.log.6.1.20.r143896.zip
(30.21 KiB) Downloaded 6 times
hottobar
 
Posts: 27
Joined: 4. Feb 2021, 11:56

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

Postby sterod » 30. Apr 2021, 19:15

I just bought a new MSI laptop with 64 GB RAM and i7-1185G7 processor. Windows 10 host.
Had same problem as you reported on the Ubuntu systems. Either it crashes after loading or does not load at all.
Was just going to send back laptop as defective, but now I saw your posts. Seems definitely to be an issue with VitualBox and i7 11th generation chips, at least the i7-1185G7.
sterod
 
Posts: 10
Joined: 30. Apr 2021, 19:08

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

Postby cri » 1. May 2021, 18:35

Same issues with Ubuntu 20.04 + VB 6.1.22 on Dell 7420 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz × 8 :
I disabled all power features (turn off of screen) and the screen saver on guest WIndows 10.
Until now I could not reproduce the issue....
cri
 
Posts: 1
Joined: 1. May 2021, 18:32

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

Postby fth0 » 6. May 2021, 18:51

As written in viewtopic.php?f=7&t=102776, borgesrsb discovered that changing System > Motherboard > Chipset to ICH9 served as a workaround for them.

@hottobar (et al.): Could you please check if this can also serve as a workaround for you for the time being?
fth0
Volunteer
 
Posts: 1969
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...

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

Postby fantic10 » 6. May 2021, 23:15

11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz 2.42 GHz
Chipset to ICH9 = it restarts anyway
fantic10
 
Posts: 8
Joined: 21. Feb 2021, 23:00

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

Postby sxc731 » 7. May 2021, 10:03

fth0 wrote:As written in viewtopic.php?f=7&t=102776, borgesrsb discovered that changing System > Motherboard > Chipset to ICH9 served as a workaround for them.

@hottobar (et al.): Could you please check if this can also serve as a workaround for you for the time being?


Also confirm crash/restart after approx. 10-15 mins despite setting VM chipset to ICH9:
  • OS: Ubuntu Hirsute (21.04)
  • Kernel: 5.11.0-16
  • VirtualBox: 6.1.18_Ubuntu r142142
  • Hardware: Intel Tiger Lake i7-1165G7, 16GB RAM (ThinkPad X1 Carbon Gen9).
  • Guest: Win10 Pro 2004 x64 (2 vCPUs, 2GB RAM)
This occurred 3 times; 1st time with VM downloading Windows updates; 2nd time running iTunes; 3rd time (after barely 1 min uptime after previous restart): VM totally idle.

The same VM works fine on the same guest under KVM/QEMU.
sxc731
 
Posts: 7
Joined: 27. Mar 2021, 18:45

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

Postby mpack » 7. May 2021, 10:45

sxc731 wrote:The same VM works fine on the same guest under KVM/QEMU.

That probably explain why it doesn't work in VirtualBox. Why would you think being built for the wrong platform helps?
mpack
Site Moderator
 
Posts: 33887
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)

Postby sxc731 » 7. May 2021, 10:47

mpack wrote:
sxc731 wrote:The same VM works fine on the same guest under KVM/QEMU.

That probably explain why it doesn't work in VirtualBox. Why would you think being built for the wrong platform helps?


Apologies, I didn't want to repeat what I wrote earlier in this thread. In the face of the VM being unusable in VB, I made a copy of its image and converted it to use with KVM/QEMU. This involved a number of steps but essentially it is the same original VM. Obviously, I use the VDI image with VB and the QCOW2 image with KVM/QEMU. I trust this clarifies??
sxc731
 
Posts: 7
Joined: 27. Mar 2021, 18:45

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

Postby mpack » 7. May 2021, 18:57

It clarifies, but it doesn't change my point. KVM/QEMU is a completely different application from VirtualBox. Whether or not a VM works in one but not in the other is completely irrelevant. In particular it doesn't tell you that one is buggy and the other not - they are just different, which we already knew.
mpack
Site Moderator
 
Posts: 33887
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)

Postby sxc731 » 10. May 2021, 10:41

I would still say that reports by 20 or so users on this thread who experienced a very similar issue with Ice/Tiger Lake CPUs; as well as my own experience that a VM derived from the same initial Win 10 Pro x64 image:
  • used to run flawlessly on previous VirtualBox laptops hosts (Intel Kaby Lake and AMD Ryzen 3700U)
  • crashes repeatedly when run on VB on new laptop (Intel Tiger Lake)
  • does not crash on that same Tiger Lake host when run on KVM/QEMU

... is pretty strong suggestion that VirtualBox is at the very least unstable (if you don't want to call it "buggy") with the combination of hosts running 10/11th gen Intel CPUs and Win 10 guests.

Don't get me wrong, I'd love to be able to go back to VirtualBox to host that VM as its usability beats KVM/QEMU hands down; however in the current state - at least in my experience and several others' here - it's simply not usable in this context.
sxc731
 
Posts: 7
Joined: 27. Mar 2021, 18:45

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

Postby hottobar » 10. May 2021, 18:13

fth0 wrote:As written in viewtopic.php?f=7&t=102776, borgesrsb discovered that changing System > Motherboard > Chipset to ICH9 served as a workaround for them.

@hottobar (et al.): Could you please check if this can also serve as a workaround for you for the time being?


Tested with VirtualBox 6.1.22 r144080 on Linux 5.10.25, with PIIX3 and ICH9 and the VM crashes with both chipsets.
Attachments
VBox.log.6.1.22.zip
(61.13 KiB) Downloaded 1 time
hottobar
 
Posts: 27
Joined: 4. Feb 2021, 11:56

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

Postby farzad_p » 10. May 2021, 18:54

I am experiencing the same issue:
Code: Select all   Expand viewCollapse view
02:25:53.052036 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffff80000002 P2=0xfffff8011bee4793 P3=0xffff890f26a0233a P4=0x7010008004002001
02:25:53.052096 GIMHv: BugCheck 1e {ffffffff80000002, fffff8011bee4793, ffff890f26a0233a, 7010008004002001}
02:25:53.052098 KMODE_EXCEPTION_NOT_HANDLED
02:25:53.052098 P1: ffffffff80000002 - exception code - STATUS_DATATYPE_MISALIGNMENT
02:25:53.052099 P2: fffff8011bee4793 - EIP/RIP
02:25:53.052099 P3: ffff890f26a0233a - Xcpt param #0
02:25:53.052099 P4: 7010008004002001 - Xcpt param #1
02:25:56.008625 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
02:25:56.843982 AHCI#0: Reset the HBA
02:25:56.843993 VD#0: Cancelling all active requests
02:25:56.844190 AHCI#0: Port 0 reset
02:25:56.845278 VD#0: Cancelling all active requests
02:26:07.277458 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x1e P1=0xffffffff80000002 P2=0xfffff8011bee4793 P3=0xffff890f26a0233a P4=0x7010008004002001
02:26:07.277620 GIM: HyperV: Reset initiated through MSR
02:26:07.277640 Changing the VM state from 'RUNNING' to 'RESETTING'
02:26:07.279613 GIM: HyperV: Resetting MMIO2 regions and MSRs

Linux Host: Linux pop-os 5.11.0-7614-generic #15~1618626693~20.10~ecb25cd-Ubuntu SMP Thu Apr 22 16:00:45 UTC x86_64 x86_64 x86_64 GNU/Linux
Guest: Windows 10
CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
VirtualBox: 6.1.18

I guess there is no workaround at the moment? And not much activity on the ticket 20180 :(
farzad_p
 
Posts: 1
Joined: 7. May 2021, 20:34

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

Postby fth0 » 10. May 2021, 18:55

Ok everyone, thanks for trying. 3 "votes" against ICH9 are enough to qualify it as no workaround.
fth0
Volunteer
 
Posts: 1969
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...

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

Postby fth0 » 20. May 2021, 02:01

@hottobar (et al.): I think I found something ... :D

Please boot your host OS with the Linux kernel parameter split_lock_detect=off and try to reproduce the problem.
fth0
Volunteer
 
Posts: 1969
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...

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

Postby hottobar » 20. May 2021, 16:13

fth0 wrote:@hottobar (et al.): I think I found something ... :D

Please boot your host OS with the Linux kernel parameter split_lock_detect=off and try to reproduce the problem.


Yes! That was apparently it!
You've probably found a good workaround! :D

I've been testing for a couple of hours and so far so good, no crashes!

The x86 32bit ISO also works.

The split_lock_detect feature was added in 5.7 along with KVM support for it.
That would explain why QEMU/KVM has no problem with Win10 on Intel CPUs.
hottobar
 
Posts: 27
Joined: 4. Feb 2021, 11:56

PreviousNext

Return to VirtualBox on Linux Hosts

Who is online

Users browsing this forum: jidethenewb and 14 guests