Closed paulmaunders closed 1 year ago
Hi Paul,
Thanks for the contribution!
How the VirtualBox vagrant boxes works on the macOS / Arm64 (M1/M2) hosts ?
Hi Elkhan, No problem! The packer build process runs and completes, but I am not able to load the vagrant boxes because the parallels tools weren't installed correctly. If Parallels can fix their tools, then I think this will work well! See: https://forum.parallels.com/threads/parallels-tools-do-not-install-on-rhel9.357546/
As I see from the changes, you also added the support for the virtualbox provider too. I wonder how the box is working on the Developer preview for macOS / Arm64 (M1/M2) hosts
The virtualbox developer preview didn't seem to work when I tried it, but I will keep trying!
==> Some builds didn't complete successfully and had errors:
--> virtualbox-iso.almalinux-9-aarch64: Error starting VM: VBoxManage error: VBoxManage: error: Unsupported CPU. (VERR_UNSUPPORTED_CPU)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
@paulmaunders what version of macOS you are using? I am getting CPU error as above in 12.5
@srbala I am using Ventura 13.0.1 (22A400)
VirtualBox does not work at all at the moment, but Parallels should build a box - it just fails to install the Parallels tools.
@paulmaunders one more, if you can create PR from a fix-branch, instead of the master branch where you can squash the multiple commits Prior to PR.
These changes add support for building 9/aarch64 vagrant boxes using the parallels provider so they can be run on M1 Macs. It mostly works, but the parallels tools do not seem to be installed correctly.