Issues after upgrading virtual box to 7.0 from 6.1.34 on Mac OSx | roll back to the same version does not work

[PushtoProd]

Hi All,

I am using Mac OSx Ventura 13. x and running virtual box 6.1.34. There are quite a few VMs running on it and all of them stopped working after I upgraded my virtual box to 7.0

The error I am getting is as:
The virtual machine 'Kali-Linux-2021.3-vbox-amd64' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}


I have tried to downgrade the virtual box to the 6.1.34 version as well however, the error still remains the same.

I had this setup of multiple labs on Vbox for my certification exam and it is extremely critical for me to get it back in working condition ASAP. Tried multiple ways over the internet to fix the issue but it stands unresolved.

Looking for some help from experts here.

Thank you for your help in advance.

[granada29]

Please post a log (zipped) of one of the failed sessions.

[PushtoProd]

Hi @Granada29 - Thank you for your response.
The log file is uploaded in the below link. Please confirm if you are able to access it.


Thanks
HA

[mpack]

We don't like offsite links, please zip the log and attach here.

[PushtoProd]

Hello,

My bad. I have attached it in the comment itself now. The same error is for all the other hosted VMs as well.

Thanks.
HA

[mpack]

There is lots of this...

00:00:01.229375 NEM: Bit 00 = UNDEFINED (AppleHV error)!
00:00:01.229393 NEM: Bit 01 = UNDEFINED (AppleHV error)!
00:00:01.229410 NEM: Bit 02 = UNDEFINED (AppleHV error)!
00:00:01.229426 NEM: Bit 03 = UNDEFINED (AppleHV error)!
00:00:01.229442 NEM: Bit 04 = UNDEFINED (AppleHV error)!
00:00:01.229458 NEM: Bit 05 = UNDEFINED (AppleHV error)!
00:00:01.229507 NEM: Bit 06 = UNDEFINED (AppleHV error)!
00:00:01.229521 NEM: Bit 07 = UNDEFINED (AppleHV error)!
...

I assume "AppleHV" means "Apple Hyper-Visor". Almost like the Apple HV feature has been disabled - is that even possible?

Followed later by...

00:00:02.363778 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900

HGCM == Host Guest Communication Manager, a component of VirtualBox.

I'm not convinced that you've installed VirtualBox properly, but I'll leave discussion of that for people like Granada29 who know infinitely more about MacOS than I do.

[PushtoProd]

Thanks for looking into this. I agree that it is possible that the installation is not done properly. Maybe as I have tried reinstalling the Vbox multiple times it is not properly installed itself.

Do you have any tried and tested ways to uninstall the Vbox and reinstall it without losing VMs? I will also wait for Granada29 to suggest further.

Thanks.

[PushtoProd]

Also, the extension file version is Oracle_VM_VirtualBox_Extension_Pack-6.1.34.vbox-extpack


These are the logs from a terminal for uninstallation.

[fth0]

I will also wait for Granada29 to suggest further.

While waiting for Granada29, there's another subtlety that I haven't understood from the beginning:

I am using Mac OSx Ventura 13. x and running virtual box 6.1.34.

You might have been able to run the VirtualBox Manager 6.1.34 on macOS Ventura 13.x, but you should not have been able to run any VirtualBox VM with this combination, because VirtualBox 6.1.x needs its own kernel extensions that are forbidden since macOS Ventura 13. Did you do something special to circumvent that?

[PushtoProd]

Hi @fth0, thanks for your assistance here.

I did not do any tweaks to make it work before the upgrade when VMs were working fine on version 6.1.
Thanks.

[scottgus1]

I did not do any tweaks to make it work before the upgrade when VMs were working fine on version 6.1.

Before you upgraded to Ventura, you could run VMs on 6.1.

After upgrade to Ventura, you cannot run VMs using 6.1.

Ventura requires uninstalling 6.1 and all its kexts. Then install 7.0.

All the uninstalling and reinstalling will leave the VMs behind to remain for the new fully-clean of 7.0 on Ventura.

[granada29]

Looks to me as if you should download VirtualBox 7.0.10 and run the uninstall script again. A number of bugs were fixed after VirtualBox 7.0.8 was released.

Then install VirtualBox 7.0.10 - dont attempt to start your VM yet.
Next - download and install the matching Oracle extensions.
Finally start a VM and see how it goes. If it fails, then please post another zipped log.

[PushtoProd]

I am so excited to share that after following the below steps. Everything worked ( All the VMs are loading now )
Though I followed the same steps very carefully earlier as well it looks like the other combination of versions had some bugs that were making it fail or I may have done a few steps incorrectly.

Also attaching the logs of a working scenario of a Kali machine just for everyone's reference (of course no analysis needed now)

Thanks a lot, everyone for your efforts in reviewing the logs and providing me suggestions to make this work finally

Good to close this thread.

Thanks.