Critical error while running virtual box

[NM]

Mack Pro Ubuntu 22.0.3 installed on Virtual box 7.0 giving critical error . attached the screen hot and logs.

[NM]

A critical error has occurred while running the virtual machine and the machine execution has been stopped.
For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the /Users/nishamohan/VirtualBox VMs/Ubuntu/Ubuntu/Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window.
Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now.

[NM]

Please advise.

[scottgus1]

I would advise zipping and posting the log file mentioned in the message, using the forum's Attachments tab.

[mpack]

But... if this "Mac Pro" has an M1 or M2 processor then see the M1/M2 sticky at the top of this forum.

[NM]

VBOX.log.zip attached to the post.

[scottgus1]

Yup, 'tis an M1/M2:

00:00:02.927231 VirtualBox VM 7.0.8_BETA4 r156879 darwin.arm64 (Apr 17 2023 18:33:44) release log
...
00:00:02.927246 OS Version: Darwin Kernel Version 22.6.0: Wed Jul 5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000

See Mpack's post above, and M1/M2 Mac 7.0 Beta Status.

[NM]

Virtual Box 7.0 beta installed on MacBook Pro Apple M1 Pro. Ubuntu installed on Virtual box 7.0 giving the critical error in the below message. Please advise on whether we have limitations on using Virtual box7.0 and Unbuntu on Apple m1 pro.

[scottgus1]

Already done. See above.

[NM]

as per the above they are development stage. currently we cannot use Virtual box 7.0 on Macbok Pro Apple M1 Pro.please confirm.

[scottgus1]

Not for modern OS's, that's correct.

The devs may get it to work one day, but it's not working now.