Opened 5 years ago
Last modified 5 years ago
#18718 new defect
VBox crashes using 32 bit Linux guest on a 64 bit Windows 10 host
| Reported by: | Martin_G | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.0.8 |
| Keywords: | Windows10 64bit | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
I've created a virtual machine with a 32 bit Linux on a Windows 7 64 bit host. Now I tried to use the same VDI disk file on a Windows 10 64 bit host computer. But when I created a new virtual machine in the current Version of VirtualBox using the existing VDI disk Image an exactly the same settings as on the Windows 7 host the virtual machine crashes ("Guru Meditation" - Fatal error) immediately after selecting the GRUB boot options in the guest.
This problem could be fixed by choosing "Linux 2.6 / 3.x / 4.x (64 bit)" as the guest OS in the "general settings" for the virtual machine -- although the Linux guest has only 32 bit (80386 32 bit ELF binaries).
Attachments (2)
Change History (3)
by , 5 years ago
comment:1 by , 5 years ago
It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. Plus a discussion and analysis on the bug tracker is going to help me, you, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...
You're getting a Guru Meditation:
00:00:20.062147 !! VCPU0: Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION)
See if the solution from #13283 helps you. From the command line enter:
VBoxManage setextradata "Crunchbang Linux" "VBoxInternal/MM/CanUseLargerHeap" 1
VBox.png - automatic screenshot on crash