Recent version of Virtualbox 7.1.0 is not supported by vagrant 2.4.1 #13501
Comments
|
Looks like the issue is caused by Virtualbox itself - checking it right now. |
|
Not confirmed. Virtualbox works fine. So, it's vagrant issue, not VB. |
|
waiting for vagrant update, a quick workaround: Edit /usr/bin/VBox |
|
Anyone has a similar workaround for Windows? |
Looks like this file is available on Linux and not on macOS. I've searched for awhile on mac and can't see the equivalent. |
@ftaiolivista thanks. Just confirming here so others can see that this worked for me on EndeavourOS (Arch-based): |
A macOS equivalent would be to edit #!/bin/bash
if [[ $@ == "--version" ]]; then
echo "7.0.0r164728"
else
exec /Applications/VirtualBox.app/Contents/MacOS/VBoxManage "$@"
fiI'm still having issues in my environment, but I don't think it's related. The error I'm encountering is the following (the vm name is nil for some reason): Running the Vagrantfile in the OP works fine, though. Edit: It actually looks like the above error is a bug with vagrant + Virtualbox 7.1. I installed 7.0, and my environment works again. |
Thanks! It fixes the issue on macOS and VB 7.1.0+. |
|
I followed the suggestion to edit For reference, here's the diff of my changes for better clarity: --- /tmp/orig/VBox 2024-09-14 15:40:52.961690431 +0200
+++ /usr/bin/VBox 2024-09-14 15:42:05.941525049 +0200
@@ -142,7 +142,11 @@
exec "$INSTALL_DIR/VirtualBoxVM" "$@"
;;
VBoxManage|vboxmanage)
- exec "$INSTALL_DIR/VBoxManage" "$@"
+ if [[ $@ == "--version" ]]; then
+ echo "7.0.0r164728"
+ else
+ exec "$INSTALL_DIR/VBoxManage" "$@"
+ fi
;;
VBoxSDL|vboxsdl)
exec "$INSTALL_DIR/VBoxSDL" "$@" |
|
Unfortunately this workaround doesn't help with M* MacOS, as arm boxes aren't picked (which VirtualBox 7.1 is meant to address) |
|
This worked for me on windows. In: Edit $ diff -u meta.rb.orig meta.rb
--- meta.rb.orig 2024-09-16 11:37:37.017440100 +0100
+++ meta.rb 2024-09-16 11:33:51.312254400 +0100
@@ -69,6 +69,7 @@
"6.0" => Version_6_0,
"6.1" => Version_6_1,
"7.0" => Version_7_0,
+ "7.1" => Version_7_0,
}
if @@version.start_with?("4.2.14")
|
|
What @aburston suggested works. Although on Mac (if you installed Vagrant with Homebrew) the location is |
This worked for me. |
|
I also landed here. I was on Linux Mint and I got this error: What I did to fix it was at the top, change the shebang from /bin/sh to /bin/bash. Worked like a dream. |
|
running temp meta.rb fix for windows fixed issue for me, make sure your machines are not in a suspended state or you will have to manually open them in virtualbox then poweroff machine, then the up signal will work correctly |
That solved my issue with the virtualbox 7.1 version, but now when i run
What could it be? |
|
For the record, I ran into a slew of problems when upgrading directly from VirtualBox 7.0 to 7.1. I had to completely uninstall 7.0 first before installing 7.1. @lerichardv Try a complete uninstall. Edit: I now get this error too. I have no fix. |
Fixes hashicorp#13501 Signed-off-by: Wong Hoi Sing Edison <[email protected]>
I have the same issue (1st problem and the second after solving 1st). There was an error while executing Command: ["startvm", "93d13001-f252-48f7-a4f5-3c92b7245391", "--type", "headless"] Stderr: VBoxManage: error: The VM session was aborted |
|
Just rollback to VirtualBox 7.0 until Vagrant adds support for 7.1. |
|
@slonopotamus thanks for your message. However I am afraid for the macOS with Silicon Chips, there is no official VirtualBox image that could be currently used. At least I did not find any on virtualbox website, only see the v7.1 supports Apple chips. Although there is an unofficial beta port in brew, that can be installed with If you know maybe you could help us (or someone else) which exact versions of Vagrant & VirtualBox are actually compatible and working with each other for Silicon Chips? |
|
7.0.8 for Apple chips is still available from https://download.virtualbox.org/virtualbox/7.0.8/VirtualBox-7.0.8_BETA4-156879-macOSArm64.dmg I have no idea whether it works with Vagrant or not. But current issue talks about "recent" versions, so I assume that not recent versions worked properly. |
|
Virtualbox 7.0 seems to have only beta support for Apple silicone and hence is giving errors for me, even if I try it manually without vagrant. And the latest patch of 7.0 has completely removed the M1 support and doesn’t even install. The best solution here would indeed be 7.1 + vagrant. |
Worked perfectly in stock Debian bookworm, same path. Thank you. |
The above workaround works. However, this is not a solution to the problem. Vagrant 2.3.7 Repo provider: |
|
I'm sure it was stated above, but if you're on MacOS (I'm on Ventura 13.7, on a 2017 MBP w/ Intel silicon), you can simply download the VirtualBox <= 7.0 such that it will be compatible with the latest version of Vagrant, and you won't have to edit any files on your system Follow Below Steps to Run Windows VM via VirtualBox/Vagrant on MacOS (Easy way I have found)1. Download link for older/previously released versions of VirtualBox:***I used version 7.0 2. Obviously have Vagrant installed (I'm using version 2.4.1)3. Clone this repo from githubhttps://github.com/StefanScherer/windows-docker-machine 4. Navigate to the newly cloned repo directory in your terminal of your choice and run the below command:Boom. It should boot up with no errors. Remember you can download the VM extensions tools for VirtualBox as-well (the link is one the same page as the older/previously released builds as they are linked to their respective build release fyi). You can use the VirtualBox GUI to operate your new VM. Good luck. |
|
Thank you, the instructions above are really appreciated and do work for those who are not dependent on Virtualbox 7.1.0, however, the issue is that |
|
need update by vagrant |
|
Also running into this issue, 2022 M2 Macbook Air VirtualBox 7.1.2 Extremely frustrating! |
|
@aburston thank you very much, it worked for me |
|
Due to the challenges in keeping support for various hypervisor versions fully up-to-date, it would be helpful to introduce a configurable variable that includes a "without warranties" option. This would allow users to opt into this setting without needing to modify the code directly. |
|
Dear Vagrant developers, please add an option to ignore installed VirtualBox version. |
|
+2 (as vote for this issue to be fixed from 2 developers) |
|
after editing the driver map, in a Mac with Apple Silicon and Vagrant 2.4.1 / VirtualBox 7.1, I'm getting: $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'bento/almalinux-9-arm64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'bento/almalinux-9-arm64'
default: URL: https://vagrantcloud.com/api/v2/vagrant/bento/almalinux-9-arm64
The box you're attempting to add doesn't support the provider
you requested. Please find an alternate box or use an alternate
provider. Double-check your requested provider to verify you didn't
simply misspell it.
If you're adding a box from HashiCorp's Vagrant Cloud, make sure the box is
released.
Name: bento/almalinux-9-arm64
Address: https://vagrantcloud.com/api/v2/vagrant/bento/almalinux-9-arm64
Requested provider: virtualbox (arm64)obviously -arm64 would be the correct image here, so... |
FWIW pulled out my hair for a bit, I have this file BUT ALSO one installed in |
|
it's been months since this was released, it there still no official support for Virtual Box 7.1? |
|
This error is not a welcoming introduction to Vagrant. Thanks to the people in this thread who found and posted a workaround. |
|
What is going on with Vagrant that they aren't updating it? This is a pretty big issue. |
There's already a pull request that is supposed to fix this issue, if you are able to help it progress it will be fixed sooner. |
|
There's one more pull request that passes all tests. |
|
there are no images for virtualbox / arm64 anyway :D so even if it fixed, it's not enough |
|
still waiting, you can temporary fix for ubuntu 24.04 sudo vim /usr/bin/VBox VBoxManage|vboxmanage)
########################
if [ "$1" = "--version" ]; then
echo "7.0.0r164728"
else
exec "$INSTALL_DIR/VBoxManage" "$@"
fi
;;
########################and then vagrant up |
|
trying out vagrant on WSL for the first time, got VirtualBox 7.1 installed on the windows host and editing |
That if they gonna release a package with this fix. Since I've been waiting for #13373 for more than half a year 😪 |
About this, anyone have tested Lima? (https://lima-vm.io/) Can be a good replacement of vagrant? |
|
Still getting error when setting up the network interface even with the latest nightly build: Error from starting new VMEnvironment: |
|
@pavelhoral can you please provide a simple |
Getting this error when using the recently released 2.4.2 release: |
and others
Debug output
https://gist.github.com/mrdc/bbde883832d21763ca9f975adb641e10
Expected behavior
Vagrant should work with the recent Virtualbox version as the backend.
Actual behavior
Vagrant doesn't work with the recent Virtualbox version as the backend.
Reproduction information
Vagrant version
Vagrant 2.4.1
vagrant-vbguest (0.32.0, global)
Virtualbox 7.1.0-r164697
Host operating system
macOS 14.6.1
Guest operating system
Ubuntu 14.04 64bit
Steps to reproduce
Vagrantfile
The text was updated successfully, but these errors were encountered: