Windows 10 Installation Fails with Virtual Box Critcal Error

[spflanze]

The attached file "Windows 10 Virtual Machine Settings 2022-09-17_17-47.png" shows the settings.

After entering the License Key, after many installation messages that appear to show the installation is making progress, I get the error shown in the attached file "Critical Machine Errro 2022-09-17_13-28.png".'

The file "Windows 10-2022-09-17-13-29-39.log" is the log.

Any help with what went wrong here would be much appreciated.

[scottgus1]

The guru pulled the "TRIPLE_FAULT" error while rebooting. This error is a last-ditch something-went-so-wrong error when the VM OS did something Virtualbox's error routines couldn't figure out.

Some suggestions:
You have 16 processors in the VM. Reduce to 2 for the install, not more, not less. More processors in the VM hurts the speed of the VM due to extra scheduling oversight in the host OS. More processors only helps when you install multi-processor-aware multi-thread 3rd-party software in the VM, which you would not have while installing the OS. Windows 10 adores two processors for out-of-the-box operation. Add more if 3rd-party software requires them, after the OS is installed and stable.

You have 64GB RAM in the VM. Reduce RAM to 4GB for the install, not more, not less. Windows has to touch all its RAM during boot, and it's faster to run through 4GB than 64GB during a boot. Add more RAM if desired, after the OS is installed and stable.

You have 3D acceleration enabled. This requires Guest Additions installed in the VM OS, which you don't have during OS installation. This adds an unneeded layer of complexity at this stage. Turn 3D off during the install, and turn it back on when you're ready to install the GAs.

When you do get 10 installed and have 3D acceleration running, you'll probably need to disable 10's Transperancy Effects, which have issues when 3D is enabled.

[fth0]

Linux kernels 5.19, 5.18, 5.17.12+ (e.g. Fedora 35 + 36), 5.15.44+ (e.g. Arch Linux 5.15.45-1-lts, Ubuntu 5.15.0-47.51) and 5.10.119+ (e.g. Debian Bullseye 5.10.0-15) and 5.4.200+ (e.g. Ubuntu 5.4.0-126.142) are only supported by VirtualBox 6.1.36 and newer.

If you're using the Oracle-provided VirtualBox version, update to VirtualBox 6.1.38. If you're using the Ubuntu-provided VirtualBox version, see https://bugs.launchpad.net/ubuntu/+sour ... ug/1988473.

[spflanze]

I used Ubuntu 22.04.1's Discover to install Virtual Box. This installed Version 6.1.34_Ubuntu r150636. What is the best way to get the latest Virtual Box version? Do I explicitly give apt the specific version to install? Is there a PPA I can install from somewhere that would do this and keep my Virtual Box installation updated when the command sequence ""apt update", and "apt upgrade", is done? Or will it be necessary to download the installation files from: https://www.virtualbox.org/wiki/Downloads ?

[fth0]

Ok, I'll assume that you've read the Ubuntu bug ticket and deliberately decided to replace the Ubuntu-provided VirtualBox by the Oracle-provided VirtualBox. To do that:

First uninstall all Ubuntu-provided "virtualbox*" packages and reboot the host. Then, read and follow the section named "Debian-based Linux distributions" on https://www.virtualbox.org/wiki/Linux_Downloads to install the Oracle-provided "virtualbox-6.1" package. Afterwards, apt will keep your VirtualBox 6.1 installation up to date.

[spflanze]

Today I saw that Discover showed an update is now available for VirtualBiox. I attempted to install this update, and got the message that it could not be done. The apt command also could not do it. So in Discover I removed VirtualBox, and reinstalled it. Discover then installed Version 6.1.38_Ubuntu r153438.

Next I attempted to install Windows 10 once again, and this time I followed scottgus1's recommendations. This is the error message I got:

Failed to open a session for the virtual machine Windows 10.

Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: Unable to locate imported symbol 'SUPR0FpuBegin' for module 'VMMR0.r0' (VERR_SYMBOL_NOT_FOUND).

Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

[scottgus1]

Unable to locate imported symbol 'SUPR0FpuBegin' for module 'VMMR0.r0' (VERR_SYMBOL_NOT_FOUND).

Please see viewtopic.php?t=106582

[spflanze]

Where is this Extension Pack for Version 6.1.38 downloaded from? The only place I can find it is here:
https://www.downloadcrew.com/article/20 ... nsion_pack
Because this does not appear to be either Virtual Box's, or Oracle's, website I do not trust it.

[mpack]

See the "Get VirtualBox" link at the bottom of every forum page.

[spflanze]

I downloaded from this link:
https://download.virtualbox.org/virtual ... ox-extpack
and added that downloaded package to my Virtual Box installation.

When I attempt to start up Windows 10 the error I get now is:

Failed to open a session for the virtual machine Windows 10.

Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: Unable to locate imported symbol 'SUPR0FpuBegin' for module 'VMMR0.r0' (VERR_SYMBOL_NOT_FOUND).

Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

The settings, and the extensions, that were in effect are attached.

[scottgus1]

Moved to Linux Hosts, as this is a host issue.

in Discover I removed VirtualBox, and reinstalled it. Discover then installed Version 6.1.38_Ubuntu

FWIW we only handle official Virtualbox on this forum. Technically you're running Ubuntu's fork, which Ubuntu supports.

Please read through this topic on the same error. viewtopic.php?f=7&t=106582

[spflanze]

According to the responses to this thread of mine:
https://askubuntu.com/questions/1431649 ... box-a-fork
The VirtualBox installed by Discover in Ubuntu 22.04.1 is not a fork.

[scottgus1]

AskUbuntu is not considered an authority here.

Any version of Virtualbox with a version x.y.z_linuxfamilyname is a fork. Official Virtualbox doesn't have the underscore & family name. You're running the fork.

How did my linked topic work for you?

[fth0]

The VirtualBox installed by Discover in Ubuntu 22.04.1 is not a fork.

You're right that it's not a fork in the usual sense, where a software project is split into two projects and the two projects are being further developed independently for a longer time (*). The major Linux distributions take the Oracle-provided VirtualBox releases and adapt them slightly to their individual infrastructure, which rather resembles a fish bone with short side bones than a fork. I usually coin that "Ubuntu-provided VirtualBox distribution" (or similar), because they are quite close in behavior to the Oracle-provided VirtualBox releases.

But the property remains that the different Linux distributions make different changes to the VirtualBox sources (mainly in the infrastructure parts), which are unknown to most moderators and volunteers here. Therefore, we often can only assess how the Oracle-provided VirtualBox releases behave. FWIW, I'd make an educated guess that in > 80% of cases the different VirtualBox distributions behave the same, and in < 20% of the cases they behave differently, but it's not negligible.

(*) If I wanted to start splitting hairs, I could mention that the majority of todays forks are the forks on GitHub, and most of them don't even have a significant amount of changes at all.

[spflanze]

I used Discover to remove the installation of VirtualBox it had installed.

From the VirtualBox.org website I downloaded the file "virtualbox-6.1_6.1.38-153438~Ubuntu~jammy_amd64.deb" and used Ubuntu's Software Installer from Dolphin to install it.

I started up VirtualBox and installed the the extension pack "Oracle_VM_VirtualBox_Extension_Pack-6.1.38.vbox-extpack"

I created a new Windows 10 Virtual Machine and configured it according to scottgus1 recommendations here at 18. Sep 2022, 14:49.

Then I attempted to start up the Windows 10 VM and got the same error:

Failed to open a session for the virtual machine Windows 10.

Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: Unable to locate imported symbol 'SUPR0FpuBegin' for module 'VMMR0.r0' (VERR_SYMBOL_NOT_FOUND).

Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}