[BUG]: Tried running MAX on Ubuntu 22.04 running on a VirtualBox on Windows 11

[GaryLuck]

Bug description

'modular install max' step fails

Steps to reproduce

(max-venv) gary@gary:~$ modular install max

Found release for https://packages.modular.com/max @ 24.4.0

Downloading archive: packages/24.4.0/max-x86_64-unknown-linux-gnu-24.4.0-6-0.tar.zst

Downloaded [ ███████ ] 100% 651MiB/651MiB

Extracting downloaded archives.

Extracted [ ███████ ] 100% 651MiB/651MiB

Running post-install scripts...

Mojo Commands [ ██▋ ] 37% [mojo][error] Mojo SDK post-install test "mojo repl" failed:
CheckError: expected '42' to appear in output:

File "/home/gary/.modular/pkg/packages.modular.com_max/scripts/checks/self-test-basic.py", line 298, in test_mojo_repl
self.assert_contains("42", out)
File "/home/gary/.modular/pkg/packages.modular.com_max/scripts/checks/self-test-basic.py", line 147, in assert_contains
raise CheckError(needle, haystack)
[mojo][error] Some components of the Mojo SDK may have been installed successfully, but others may not work as expected.
[mojo][error] Please submit an issue to https://github.com/modularml/mojo and include the full output of the command you just ran.
Mojo Commands [ ██▋ ] 37%
modular: error: failed to run script

System information

- What OS did you do install MAX on ? Ubuntu server on Virtual Box on Windows 11
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

- Provide version information for MAX by pasting the output of max -v`
max did not get built
  
- Provide version information for Mojo by pasting the output of mojo -v`
mojo did not get built

- Provide Modular CLI version by pasting the output of `modular -v`
modular 0.9.2 (b3079bd5)

[rainflood]

It maybe VirtualBox is running without Hyper-V enabled, you can follow the tips in https://forums.virtualbox.org/viewtopic.php?t=99390, I just solved the same problem yesterday.