macOS Monterey and VirtualBox 6.1.28 #12557
Comments
|
Absolutely the same issue here too. |
|
Same problem here after upgrading to Monterey vagrant up |
|
Same problem here. |
|
Same issue with Monterey. |
|
A workaround I've found is to enable the VirtualBox GUI in the Vagrantfile. |
Can confirm, it worked as a workaround for me. Thanks!! |
I can confirm that workaround worked with me as well. However, the IP address on the VM was not set to the one from the Vagrantfile / config.vm.network 'private_network', ip: '11.0.0.12' /. |
|
For me it stuck at `==> default: Mounting NFS shared folders... mount -o vers=3,udp 192.168.50.1:/System/Volumes/Data/Users/[localtion]/vagrant-nfs-marcin.test Stdout from the command: Stderr from the command: mount.nfs: Connection timed out |
I ran into this as well. Using |
It stuck probably due to the same reason with the incorrect IP address set to the VM. It seems that with the workaround it's not setting the correct IP address. |
|
For me, it is still showing this error There was an error while executing Command: ["hostonlyif", "create"] Stderr: 0%... |
|
after enabling the VirtualBox Gui, then ran these commands: sudo kextload -b org.virtualbox.kext.VBoxDrv sudo kextload -b org.virtualbox.kext.VBoxNetFlt sudo kextload -b org.virtualbox.kext.VBoxNetAdp sudo kextload -b org.virtualbox.kext.VBoxUSB then it worked for me. |
|
For me @rockblings solution haven't bring a temporary solution. Still stuck on Mounting NFS shared folders Running command => vagrant up |
I am having same issue :( |
|
I think it may be related with Virtualbox running in headless mode. It looks like this issue here: https://www.virtualbox.org/ticket/20636 |
|
I tried combination of @dsutphin and @rockblings solutions and it worked a bit but not fully. I am using: I did this:
But I have following config in my Vagrantfile And these are not working, so vagrant up but it is not able to forward ip properly and hence I cannot access it via local domains pointed to that ip in hosts file. Please help if anyone knows about how to fix this IP thing now. |
|
Same complains in the Virtalbox's forum as well https://forums.virtualbox.org/viewtopic.php?f=8&t=104249&p=507889 |
|
Forgot to mention that the solution that works for me did not work with VirtualBox 6.1.28. so i downgraded to 6.1.26. then it worked after uninstalling and installing the 6.1.26. i hope this helps |
This seems to work for me too. Thank you! |
|
We noticed this issue when we upgraded to Virtualbox 6.1.28 on BigSur 11.6 the other day, downgrading to Virtualbox 6.1.26 fixed the issue and allowed the box to boot up. |
|
I can confirm that adding |
Did NOT work for me without |
|
I can also confirm that downgrading to 6.1.26 and adding config.vm.provider "virtualbox" do |v| to the project Vagrantfile allowed me to run the project |
|
Worked for me just adding: Homestead.yaml ip: "192.168.10.10" vagrant 2.2.18 |
And IP address was correctly set to 192.168.10.10 ? |
yes, I uninstall 6.1.26 and install 6.1.28, do https://www.virtualbox.org/ticket/20636 короче все работает на последней версии VB, перестанавливал обе версии 6.1.26 и 6.1.28, появляется маленький экран вертуалки - сворачиваешь его и все |
|
I can confirm that VirtualBox 6.1.26 respects the IP address configured into the Vagrantfile. Version 6.1.28 - did NOT! |
|
According to this ticket: https://www.virtualbox.org/ticket/20626 there is some change about host-only networking on the newest 6.1.28 VirtualBox. Probably thats why IP addresses set from the Vagrantfile are not respected? |
|
Same issue Here
|
Work for me! |
It works for me without the "private_network" part, thanks! |
With a fresh install of Monterey and all of the applications, this finally worked for me. |
|
I want to summarize what helped me based on all the valuable input above.
This combination is working for me. If I use
|
|
I spent a long time solving the issue of virtualbox and switched to docker and this was my best solution, a solution to work with docker and forget about vagrant and virtualbox problems |
|
I too have finally lost patience with VirtualBox with niggles for months and finally total failure with Monterey, and, since I had Parallels Desktop already on my Mac, using |
|
I downgraded to Big Sur and doesn't have any problems with 6.1.26. I use Vagrant and Virtualbox with https://roots.io/docs/trellis/master/installation/#create-a-project - both are required. |
|
First of all you need to have 6.1.28 on Monterey to prevent kernel panics. The second issue with not loading the kexts automatically is because the file Not sure why oracle didn't change this yet. |
Unfortunately it still does not work at all. Using 6.1.28 and fixing those lines in VirtualBoxStartup.sh still causes kernel problem while starting the vm. :( Am I missing something or is it currently impossible to use macOS Monterey and Vagrant (with VirtualBox)? |
This will fix one of the issues. I also restarted VBox: It seems there's another an ongoing issue with Then the I'm on MacOS 12.0.1: |
|
Hi everyone, To summarize this issue, there are currently issues with VirtualBox on macOS Monterey. There's three different things which are causing issues:
For 1, the only way to workaround this is to enable the GUI within the provider configuration: config.vm.provider :virtualbox do |vb|
vb.gui = true
endFor 2, the kernel extensions can be loaded manually (which may be required after reboot): sudo kextload -b org.virtualbox.kext.VBoxDrv;
sudo kextload -b org.virtualbox.kext.VBoxNetFlt;
sudo kextload -b org.virtualbox.kext.VBoxNetAdp;
sudo kextload -b org.virtualbox.kext.VBoxUSB;For 3, the 6.1.28 release introduced a new restriction when creating networks which can be found here. PR #12564 adds validation to given addresses and returns back useful error message for how to add more ranges to the VirtualBox configuration. Unfortunately there is nothing we can do directly to resolve these issues (outside of the networking issue which will be included in the next release). The next maintenance release of VirtualBox should include fixes for the other two issues. Cheers! |
To hopefully help some others out there, I'm using Trellis from roots.io. I did all of the above steps, but I was hanging while trying to get admin privileges for mounting NFS shared folders. I was typing my password into the prompt, but then the system would still ask privileges from a system modal. I'd do that, then it would still hang (and timeout eventually), right on this part: As another user mentioned:
After re-installing VirtualBox to 6.1.26 (and accepting the privacy request from Oracle, then rebooting my system), my Trellis VM works once again. And yes, you do have to run those commands after restarting your computer (every time). |
Same issue |
This worked for me. VM is running, thank you! |
|
What i did to make it work was:
Than i had "Kernel driver not installed (rc=-1908)" error and to fix this i just: after this everything worked like it was supposed to |
This works for me with Laravel Homestead, I didn't need to destroy the machine |
|
Headless on VirtualBox version 6.1.29 is working again, not sure if Vagrant is, someone needs to test it since i'm not using it. https://www.virtualbox.org/wiki/Testbuilds |
|
Same roblem Failed to open a session for the virtual machine dashboard. The virtual machine 'dashboard' has terminated unexpectedly during startup with exit code 1 (0x1).
|
Installed them, tried to run create a new instance of Ubuntu didn't work, tried to run headless didn't work either |
|
I was able to get my VM up and running again with the new macOS update by adding this to the Vagrantfile My current setup has: Vagrant version: 2.2.18 |
|
Hi everyone, I'm locking this issue to help people locate the information they need. For a summary of the current issues with Vagrant using the VirtualBox provider on macOS, please see this comment: #12557 (comment) I've locked the issue as "resolved" since the things that can be addressed by Vagrant (network range validation) has already been completed and will be available in the upcoming release. The other issues being encountered will be fixed once VirtualBox publishes their next maintenance release. Workarounds for these issues can also be found in this comment: #12557 (comment) Cheers! |
chrisroberts
changed the title
and others
Hello. I am having some issues with running
vagrant upin Mac OS Monterey 12.0.1.I am running Virtual Box version 6.1.26 (I have tried 6.1.28, same problems) and Vagrant version 2.2.18.
During the installation of VBox I did went into System Preferences -> Privacy -> Allow Oracle....
So, the first problem is the following:
However, when I load the kexts (found this suggestion in other threads) by running
sudo kextload -b org.virtualbox.kext.VBoxDrv sudo kextload -b org.virtualbox.kext.VBoxNetFlt sudo kextload -b org.virtualbox.kext.VBoxNetAdp sudo kextload -b org.virtualbox.kext.VBoxUSBit throws me another error which I could not find any solution for.Is this some problem with MacOS Monterey? Thanks!
The text was updated successfully, but these errors were encountered: