VirtualBox 6.1 was released on the 11th of December and I totally missed it.
The downloads and changelog are in the usual places.
I spotted it this morning, downloaded it and installed in straight away. I had no installation dramas on Windows 10, macoS Catalina and Oracle Linux 7 hosts.
The problem *for me* was the current version of Vagrant (2.2.6) doesn’t support VirtualBox 6.1 yet. I can’t live without Vagrant these days, so I installed VirtualBOx 6.0.14 again and normal life resumed. See Update.
I’m sure there will be a new release of Vagrant soon that supports VirtualBox 6.1, but for now if you use Vagrant, don’t upgrade to VirtualBox 6.1 yet. I’m sure you won’t have to wait long… See Update.
Cheers
Tim…
Update 1 : A couple of people Peter Wahl and Andrea Cremonesi pointed me at this post by Simon Coter, which contains config changes to allow Vagrant 2.2.6 to run with VirtualBox 6.1.
Update 2 : I’ve followed Simon’s post and it worked fine. If you are using Windows 10 as the host and have done a default installation of Vagrant, the files he’s discussing are in these directories.
C:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6\plugins\providers\virtualbox\driver\ C:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6\plugins\providers\virtualbox\
Update 3 : I updated by work PC also. It required a couple of reboots to get things working. I think it may be something to do with the way we do security here. It’s working fine now.
Hi Tim, just a quick note to warn users of recent Mac (with Core i9) that there seems to be a major issue with VirtualBox 6.x that causes kernel panic when starting VM.
Happy New Year
Jean-François Brodeur
PS details to be found on macOS forum https://forums.virtualbox.org/viewforum.php?f=8
# Patch Vagrant 2.2.6 to work with VirtualBox 6.1 in 3 steps :
1) D:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6\plugins\providers\virtualbox\driver\
Edit the file meta.rb and add to the map driver_map :
“6.1” => Version_6_1,
2) D:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6\plugins\providers\virtualbox\driver
Copy the file version_6_0.rb as version_6_1.rb
Edit the new file version_6_1.rb
– Remplace
# Driver for VirtualBox 6.0.x
class Version_6_0 < Version_5_0
By
# Driver for VirtualBox 6.1.x
class Version_6_1 < Version_6_0
– Remplace
@logger = Log4r::Logger.new("vagrant::provider::virtualbox_6_0")
By
@logger = Log4r::Logger.new("vagrant::provider::virtualbox_6_1")
3) D:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6\plugins\providers\virtualbox
Edit the file Plugin.rb and add to the module Driver :
autoload :Version_6_1, File.expand_path("../driver/version_6_1", __FILE__)
Yobo: I know. That’s why I linked to Simon Coter’s post about this in the update section, which explain this.
Thanks Tim (I read your post a little quickly.). Your post helped me a lot 😉
Happy New Year 2020 !!
While I don’t use Vagrant, Minishift and IBM Cloud Private seem to as they have been failing on my Mac. It seems to be related to changes to the VBoxManage command-line arguments and networking. Downgrading VirtualBox to 6.0 resolved the startup issues, but VirtualBox seems to be unstable.
The UI occasionally freezes (particularly when multi-selecting hosts to startup/shutdown). Some VM’s are not completely shutdown, and VBoxManage hangs when I use it to attempt to power off the guest and the only option is to kill the PID.
I uninstalled 6.1 with AppCleaner but left all the configuration and other directories intact and only removed the .app file. Perhaps some configuration leftover from 6.1 is causing the issue.
Have you experienced any issues since downgrading?
I only downgraded for a short time, then upgraded again. 🙂 During that time I didn’t have a problem though.
I’ve downgraded before by removing and reinstalling, and never had a problem those time.
If you are having problems, file a bug with the team. https://www.virtualbox.org/wiki/Bugtracker
They are usually pretty responsive, and maintenance releases come through pretty quickly.
Cheers
Tim…