VM Installed on Mac Monterey M1 Pro - Crash during Windows 10 ISO Install

[SYod]

00:00:00.610850 VirtualBox VM 7.0.0_BETA4 r153978 darwin.arm64 (Oct 6 2022 22:02:35) release log
00:00:00.610856 Log opened 2022-10-21T14:58:15.372987000Z
00:00:00.610857 Build Type: release
00:00:00.610868 OS Product: Darwin
00:00:00.610870 OS Release: 21.6.0
00:00:00.610872 OS Version: Darwin Kernel Version 21.6.0: Mon Aug 22 20:19:52 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T6000
00:00:00.610922 Firmware type: failed - VERR_NOT_SUPPORTED
00:00:00.610935 Host RAM: 16384MB (16.0GB) total, 7167MB (6.9GB) available
00:00:00.610936 Executable: /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM
00:00:00.610937 Process ID: 8670
00:00:00.610937 Package type: DARWIN_64BITS_GENERIC
00:00:00.611913 Installed Extension Packs:
00:00:00.611931 Oracle VM VirtualBox Extension Pack (Version: 7.0.0 r153978; VRDE Module: VBoxVRDP; Crypto Module: VBoxPuelCrypto)
00:00:00.613469 Console: Machine state changed to 'Starting'
00:00:00.613584 Qt version: 6.3.0
00:00:00.615698 SUP: In driverless mode.
00:00:00.618990 Guest OS type: 'Windows10_64'
00:00:00.620973 fHMForced=true - No raw-mode support in this build!
00:00:00.628350 File system of '/Users/XXXXXXX/VirtualBox VMs/Windows/Snapshots' (snapshots) is unknown
00:00:00.628373 File system of '/Users/XXXXXXX/VirtualBox VMs/Windows/Windows.vdi' is apfs
00:00:00.630715 File system of '/Users/XXXXXXX/Downloads/Win10_22H2_English_x64.iso' (DVD) is apfs
00:00:00.633930 File system of '/Users/XXXXXXX/VirtualBox VMs/Windows/Unattended-66aec996-5bcc-46a5-9dd7-afbdd5200615-aux-floppy.img' (Floppy) is apfs

[scottgus1]

Please see the M1/M2 sticky in the Mac Hosts forum.

[mpack]

Not that it matters, but why are you still running a 7.0.0 beta?

[fth0]

Not that it matters, but why are you still running a 7.0.0 beta?

Because it's the only (and newest) VirtualBox for M1 version?

[SYod]

I'd be happy to use another non-beta version that works on M1. Where would one find that? Thanks ScottGus1, checking posts now.

[mpack]

No version of VirtualBox works on M1. A developer preview slipped out containing a non-useful build, that's it. Judging from the interest in it, apparantly there's a lot of desperate M1 users out there with buyers remorse?

[fth0]

Judging from the interest in it, apparantly there's a lot of desperate M1 users out there with buyers remorse?

IMHO it's not an Apple Silicon (M1/M2) specific problem: Sooner or later, many new users of macOS and Linux OSes (Intel/AMD and ARM) discover that they're missing a suitable (*) replacement for one of their favorite Windows-only applications.

(*) To give a common example: Most Windows users probably use Microsoft Office, and it took them a lot of effort to learn where to find the buttons and menu items important to them. Although they could switch to LibreOffice on macOS and/or Linux in terms of available functionality, they won't do that.