Debian ARM64 fails on M1 - VERR_HGCM_SERVICE_NOT_FOUND
-
- Volunteer
- Posts: 771
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Debian ARM64 fails on M1 - VERR_HGCM_SERVICE_NOT_FOUND
VirtualBox 7.1.0 beta2
Debian ARM64 VM - previously working on 7.1.0-beta
The VM crashes almost instantly under beta 2.
Debian ARM64 VM - previously working on 7.1.0-beta
The VM crashes almost instantly under beta 2.
-
- Volunteer
- Posts: 1249
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux, BSD
- Location: United Kingdom
Re: Debian ARM64 fails on M1 - VERR_HGCM_SERVICE_NOT_FOUND
@granada29
My Debian 12.5 VM seems to be working fine on Beta 2 (on an M1 Max) but our logs don't seem remotely similar, so I'm struggling with the 'interpretation' of what's happening. They both seem to be very different to the 'old x86 style' output I thought I was beginning to get used to.
I can provide a copy of a log from my working Debian 12.5 VM if it's of any interest for comparison.
My Debian 12.5 VM seems to be working fine on Beta 2 (on an M1 Max) but our logs don't seem remotely similar, so I'm struggling with the 'interpretation' of what's happening. They both seem to be very different to the 'old x86 style' output I thought I was beginning to get used to.
I can provide a copy of a log from my working Debian 12.5 VM if it's of any interest for comparison.
-
- Volunteer
- Posts: 771
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: Debian ARM64 fails on M1 - VERR_HGCM_SERVICE_NOT_FOUND
Seeing a working log would be helpful thanks.
I am running under the most recent Sequoia Beta, so this may be another cause of failure.
I also tried running an x86 Debian VM (with the 'global' flag set), and that worked perfectly.
Just now I tried uninstalling VBox Beta 2 and reinstalling. That made no difference.
I am running under the most recent Sequoia Beta, so this may be another cause of failure.
I also tried running an x86 Debian VM (with the 'global' flag set), and that worked perfectly.
Just now I tried uninstalling VBox Beta 2 and reinstalling. That made no difference.
-
- Volunteer
- Posts: 1249
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux, BSD
- Location: United Kingdom
Re: Debian ARM64 fails on M1 - VERR_HGCM_SERVICE_NOT_FOUND
Sound's as if you are having endless fun!
Hope the attached provides some clues, or is at least educational.
Hope the attached provides some clues, or is at least educational.
-
- Volunteer
- Posts: 771
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: Debian ARM64 fails on M1 - VERR_HGCM_SERVICE_NOT_FOUND
Thank you for posting your Log. I rebooted the M1 in Sonoma, installed VBox Beta 2 and now the arm64 VM runs perfectly.
Looks like the error I saw is something to do with the new access permissions or changes to the hypervisor introduced in Sequoia. Here's hoping Oracle are seeing the same issue
Looks like the error I saw is something to do with the new access permissions or changes to the hypervisor introduced in Sequoia. Here's hoping Oracle are seeing the same issue
-
- Volunteer
- Posts: 1249
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux, BSD
- Location: United Kingdom
Re: Debian ARM64 fails on M1 - VERR_HGCM_SERVICE_NOT_FOUND
Thanks, that's something to keep an eye open for. Apple seems to be behaving more and more like Microsoft when it comes to version updates, especially around the implementation of 'system security' changes.
-
- Oracle Corporation
- Posts: 309
- Joined: 19. May 2008, 16:09
- Primary OS: Ubuntu other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Too many to specify!
- Contact:
Re: Debian ARM64 fails on M1 - VERR_HGCM_SERVICE_NOT_FOUND
Did you try deleting the .nvram file in the VM's folder? Then try starting the VM again.
-
- Volunteer
- Posts: 771
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: Debian ARM64 fails on M1 - VERR_HGCM_SERVICE_NOT_FOUND
@pentagonix
I renamed the x.nvram file to x.nvram.save and the VM still fails on startup with the same error.
I renamed the x.nvram file to x.nvram.save and the VM still fails on startup with the same error.
Re: Debian ARM64 fails on M1 - VERR_HGCM_SERVICE_NOT_FOUND
Thanks for noticing, this is indeed caused by running the Sequioa Beta. Will be fixed in the next update.
-
- Volunteer
- Posts: 771
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: Debian ARM64 fails on M1 - VERR_HGCM_SERVICE_NOT_FOUND
Pleased to note that this problem is fixed in Test Build VirtualBox-7.1.0_BETA2-164697-macOSArm64 on Sequoia Beta RC