-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
arm64 Compatibility #49
Comments
Thanks for reporting! What other hypervisors would work on M1? We already have made some progress for libvirt, maybe we can also add another one. |
To be honest I have no experience with VMs, so I cannot recommend anything. Do you suggest that I could somehow make it work with libvirt? |
I see that libvirt-m1 is on homebrew, so in principle this can work. @fsimonis added the libvirt support here with #25. This will take an hour or two of building (maybe shorter on M1), but it would be very helpful if you could give us some feedback if this works. As stated in the README, please clone this repository and run: If this works, we can already invest more time in polishing and packaging this. |
Funilly enough, I just checked the VirtualBox webpage again and now they are offering a Developer preview for macOS / Arm64 (M1/M2) hosts ( which wasn't there yesterday ) so I'll give this a try! |
@ckarampa did you manage to solve this? If yes, how? Any feedback on this would be very helpful. 😄 |
Hey! I tried to use the developer preview of VirtualBox I mentioned, but couldn't make it work. This was all during a hands-on session, so I preferred to work with another participant on their PC instead of trying to make it work on my system and missing the whole thing. I have not tried it since though, I am sorry. |
Tried installing the VM for a hands-on session on a MacBook with Apple M1 Pro processor.
Vagrant can be installed via brew and works fine.
VirtualBox is not compatible with arm architecture chips, and from what I saw it cannot work with Rosetta. ( https://forums.virtualbox.org/viewtopic.php?t=98742 ). I guess there is not much you can do in terms of fixing it, but maybe there is an alternative for arm systems.
The text was updated successfully, but these errors were encountered: