adafruit / Adafruit-Pi-Kernel-o-Matic

https://learn.adafruit.com/raspberry-pi-kernel-o-matic
94 stars 16 forks source link

vagrant up fails to run on MacOS BigSur #23

Open subatomicglue opened 2 years ago

subatomicglue commented 2 years ago

I installed these two packages on MacOS BigSur, and reboot, and gave Oracle corp access in System Preferences / Security & Privacy / General, and VirtualBox.app access in accessability and input monitoring and allowed access to Downloads Folder...

I first tried brew install virtualbox vagrant, which gave the same error below, then I brew uninstalled, and tried the dmg files directly:

> git clone https://github.com/adafruit/Adafruit-Pi-Kernel-o-Matic Adafruit-Pi-Kernel-o-Matic

> cd Adafruit-Pi-Kernel-o-Matic

> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty32' version '20190514.0.0' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

Ideas? How do I troubleshoot this?

subatomicglue commented 2 years ago

I added to Vagrantfile

v.gui = true
image
subatomicglue commented 2 years ago

I've also tried the VirtualBox_Uninstall.tool script, rebooted, and reinstalled the VirtualBox.pkg, rebooted, same...

subatomicglue commented 2 years ago

I verified that vagrant itself does work:

vagrant init hashicorp/bionic64
vagrant up
vagrant ssh

works...

ladyada commented 2 years ago

this project is basically EOL but if you get it working let us know and we'd accept a PR to fix any deprecations! :)