Just updated to 7.0 and got error message...

[NorbyD]

Hi all,

I just upgraded to 7.0 on my Mac (10.15.7 Catalina) and got this error message:

Your device ran into a problem and needs to restart. We'll restart it for you.

First of all, it didn't restart as stated. I tried quitting VB and restarting and also tried
to restart my Mac. Still didn't resolve anything.

Please advise.

Thanks!

[scottgus1]

got this error message:

On what? The host computer OS? The VM's OS?

[NorbyD]

got this error message:

On what? The host computer OS? The VM's OS?

On the VM.

Actually, on the second thought maybe I need to update the Windows OS I'm using to run VB?
It's been awhile since I ran Virtualbox - probably about a year. My memory is a bit rusty - trying to
remember...LOL.

Thanks.

[scottgus1]

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)

[NorbyD]

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)

I think this is what you requested, I appreciate your help!:

[mpack]

Looks like a guest OS kernel driver crashed, but it was a good 80 seconds after the GAs were loaded, so the driver may not be related to VirtualBox at all. The VM keeps running after the guest OS crash.

00:00:24.009884 VMMDev: Guest Additions information report: Version 6.1.32 r149290 '6.1.32'
...
00:01:39.701141 GIM: HyperV: Guest indicates a fatal condition! P0=0xa P1=0xb8 P2=0x2 P3=0x0 P4=0xfffff801482a185a
00:01:39.722705 GIMHv: BugCheck a {b8, 2, 0, fffff801482a185a}
00:01:39.722707 IRQL_NOT_LESS_OR_EQUAL
00:01:39.722707 P1: 00000000000000b8 - memory referenced
00:01:39.722707 P2: 0000000000000002 - IRQL
00:01:39.722708 P3: 0000000000000000 - bitfield
00:01:39.722708 b0: 0 - read operation
00:01:39.722708 b3: 0 - execute operation
00:01:39.722708 P4: fffff801482a185a - EIP/RIP
00:01:42.401461 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago

Still, if you can revert to VirtualBox 6.1.32 then I would, then uninstall the GAs from the VM, then update VirtaulBox again. See if you still get the crash with no GAs.

[NorbyD]

Looks like a guest OS kernel driver crashed, but it was a good 80 seconds after the GAs were loaded, so the driver may not be related to VirtualBox at all. The VM keeps running after the guest OS crash.

00:00:24.009884 VMMDev: Guest Additions information report: Version 6.1.32 r149290 '6.1.32'
...
00:01:39.701141 GIM: HyperV: Guest indicates a fatal condition! P0=0xa P1=0xb8 P2=0x2 P3=0x0 P4=0xfffff801482a185a
00:01:39.722705 GIMHv: BugCheck a {b8, 2, 0, fffff801482a185a}
00:01:39.722707 IRQL_NOT_LESS_OR_EQUAL
00:01:39.722707 P1: 00000000000000b8 - memory referenced
00:01:39.722707 P2: 0000000000000002 - IRQL
00:01:39.722708 P3: 0000000000000000 - bitfield
00:01:39.722708 b0: 0 - read operation
00:01:39.722708 b3: 0 - execute operation
00:01:39.722708 P4: fffff801482a185a - EIP/RIP
00:01:42.401461 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago

Still, if you can revert to VirtualBox 6.1.32 then I would, then uninstall the GAs from the VM, then update VirtaulBox again. See if you still get the crash with no GAs.

Hi, thanks.

What if I delete my existing VB and reinstall it as new? Would this work? Thanks!

[granada29]

@mpack
This thread should be moved to MacOS X hosts - NorbyD has a Windows guest under macOS Catalina.

@NorbyD
This same problem was covered recently in a thread in the MacOS X Hosts forum. See: viewtopic.php?f=8&t=108461#p531304

I think your MacMini 6,1 is probably under-powered for VirtualBox 7.0 and for now you are better off to use VirtualBox 6.1.42.
I had dreadful results when I tried using VirtualBox 7 on my Macmini 6,2 so reverted to VirtualBox 6.1.x with very good results.

[NorbyD]

How do I revert back? What is the easiest way? Thanks!

[granada29]

Uninstall VirtualBox 7.0.x using the VirtualBox_Uninstall.tool script on the VirtualBox disk image you used to install the software.

To run this script, right-click and select 'Open' from the popup menu. You will get a warning that the script is unsigned but this can be safely ignored. The script will not remove your existing VMs but it's always a good idea to have a backup.

The process I use to install VirtualBox 6.1.x is outlined at: viewtopic.php?f=8&t=104589#p509874

[mpack]

Topic moved to "Windows Guests".

[NorbyD]

Uninstall VirtualBox 7.0.x using the VirtualBox_Uninstall.tool script on the VirtualBox disk image you used to install the software.

To run this script, right-click and select 'Open' from the popup menu. You will get a warning that the script is unsigned but this can be safely ignored. The script will not remove your existing VMs but it's always a good idea to have a backup.

The process I use to install VirtualBox 6.1.x is outlined at: viewtopic.php?f=8&t=104589#p509874

Before I read this, I went on the VB site and downloaded 6.1. It seemed to automatically remove 7.0 and put 6.1 in it's place.
It runs now but seems snail slow as before. I was hoping 7.0 would work and be much faster...LOL.
I'll see if I can configure it, if you have any tips let me know. Thanks again!

[granada29]

Please post another log - there may be some changes required in your configuration that would help.

I generally adjust a couple of Security&Privacy settings as well.

Open and unlock System Preferences -> Security&Privacy
Click the Privacy tab
Navigate to Accessibility and remove/disable VirtualBox and VirtualBoxVM if they are present
Navigate to Input Monitoring and remove/disable VirtualBox and VirtualBoxVM if they are present

[NorbyD]

Please post another log - there may be some changes required in your configuration that would help.

I generally adjust a couple of Security&Privacy settings as well.

Open and unlock System Preferences -> Security&Privacy
Click the Privacy tab
Navigate to Accessibility and remove/disable VirtualBox and VirtualBoxVM if they are present
Navigate to Input Monitoring and remove/disable VirtualBox and VirtualBoxVM if they are present

I cleared the VB/VMs in the Privacy settings. They were in both areas.

Here's the log, thanks again!

[granada29]

Overall it looks good. I think you should update the Guest Additions from 6.1.32 to match the VirtualBox 6.1.42 version you are now running. Not sure that will give you better performance, but it does eliminate any bugs that have been fixed since 6.1.32

Ram is tight at 3.0GB, but as long as you are careful what else is running on the host you should be OK.