Skip to content
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

Support MacOS hosts by moving to VBox 7.1 #39

Open
ralphlange opened this issue Jan 24, 2025 · 8 comments
Open

Support MacOS hosts by moving to VBox 7.1 #39

ralphlange opened this issue Jan 24, 2025 · 8 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@ralphlange
Copy link
Contributor

With version 7.1, VirtualBox supports MacOS on Apple silicon (https://www.virtualbox.org/)
That could enable us to have MacOS as an additional host OS and a unified VM environment across all.

Vagrant supports VirtualBox 7.1 (last year, it didn't). (https://developer.hashicorp.com/vagrant/docs/providers/virtualbox)

A task with possibly two independent subtasks:

  1. Get the training VM working on Apple silicon in a manually created VBox 7.1
  2. Add the Vagrant setup to create the VM on Apple silicon.

Needs Apple users to help!
@kasemir @eddybl @hjunkes @TKorhonen

@ralphlange ralphlange added enhancement New feature or request help wanted Extra attention is needed labels Jan 24, 2025
@Mrcl3
Copy link
Contributor

Mrcl3 commented Jan 24, 2025

Vagrant 2.4.3 works on Ubuntu 24 with VirtualBox 7.1. I tried with bento/rockylinux-9.

@ralphlange
Copy link
Contributor Author

ralphlange commented Jan 25, 2025

Vagrant 2.4.3 and VBox 7.1.6 work fine on Windows 11: tried rockylinux/9 and bento/ubuntu-24.04

@eddybl
Copy link
Contributor

eddybl commented Jan 28, 2025

First note: Vagrant suggests to install vagrant via brew, but the brew version is not correctly updated to 2.4.3: hashicorp/homebrew-tap#294, which currently requires to manually download the latest version

@eddybl
Copy link
Contributor

eddybl commented Feb 20, 2025

Just to update this: virtual box works with the new Macs now and it is possible to install Rocky Linux aarch64

The issue with the Phoebus documentation ( #13 ) remains (there are actually quite a lot of JavaFX errors, but Phoebus itself and the Demo panels still run properly)

The second issue remains bluesky. The container which is provided is based on x86_64 architecture. I tried building with an aarch64 supported base image jupyter/minimal-notebook:aarch64-latest instead of jupyter/minimal-notebook:latest, but as this also seems to be based on a different Ubuntu base image issues crop up while trying to install the requirements.txt for some of the packages which have to be built

@simon-ess
Copy link

@eddybl - I was not able to get virtual box to work with M2 macs. The error I get when trying to run vagrant up rocky is

Vagrant was unable to detect a disk controller with any of the
following supported types:

IntelAhci ,PIIX4 ,PIIX3 ,ICH6 ,LsiLogic ,BusLogic

Please add one of the supported controller types in order to use the
disk configuration feature.

There appears to be an enhancement request about this: hashicorp/vagrant#13586

How did you get around this?

@eddybl
Copy link
Contributor

eddybl commented Mar 5, 2025

Yeah that might have not been clear with my last answer, but I gave up with vagrant at some point.

I tried to follow the instructions to manually set up the training VM to see how far I get without the additional possible complications

@betalb
Copy link

betalb commented Mar 20, 2025

@simon-ess Linked issue was merged, not sure when it will be released, but vagrant can be easily monkey-patched, just add below snippet to your Vagrantfile

class VagrantPlugins::ProviderVirtualBox::Model::StorageController
    SCSI_CONTROLLER_TYPES = ["LsiLogic", "BusLogic", "VirtioSCSI"].map(&:freeze).freeze
end

Also bento released plenty on boxes built for virtualbox arm64

@ralphlange
Copy link
Contributor Author

That sounds promising! Thanks a lot.

@eddybl, @simon-ess: Please try that snippet, so we can add it to the Vagrantfile until the merged fix comes down the release path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants