polewws.blogg.se - Vagrant virtualbox provider

VirtualBox and Vagrant are tools I use to make my life easier, not an end in themselves, so I don’t have the time to keep working on this. I’m going to switch to VirtualBox 6.1.40 for the moment. Update 2: After a couple of successes starting up VMs using VirtualBox 7.0.2 and Vagrant 2.3.2, it all seems to have caved in now. The guest additions will be out of date, but it should still work fine, I hope. I’ll upload them to Vagrant Cloud and attempt to use them with VirtualBox 7.0.2. I’ve downgraded my Windows 10 PC to use VirtualBox 6.1.40 and I’m building new Vagrant boxes on that. It seems the kickstart is not working, like the networking on VirtualBox 7.0.2 is screwed up somewhere. I’ve tried on Windows 10, Windows 11 and macOS (Intel) and all result in the same issue. The bad news is I can’t get Packer to work, so I’m unable to build new Vagrant boxes with the 7.0.2 guest additions. Update 1: The good news is VMs seem to start OK now using Vagrant 2.3.2 and VirtualBox 7.0.2. If this doesn’t work out, I’ll be reverting to VirtualBox 6.1.40… I’ll be attempting some new Packer builds of my Vagrant boxes, then working through my Vagrant and Docker builds to add in the new patches.

provider/virtualbox: Add support for VirtualBox 7.0.

Vagrant 2.3.2 has a single feature in its changelog. Vagrant 2.3.2Īs mentioned in my post about VirtualBox 7.0, Vagrant 2.3.1 doesn’t support VirtualBox 7.0 directly, so I was expecting a quick release of Vagrant and here it is. I’ve installed 7.0.2 on a couple of Windows machines (10 and 11), and I’m going to play with it today.

Main: Fixed issue when VBoxSVC could become unresponsive if Extension Pack was not installed (bug #21167).

I’m hoping this fix solves a lot of my problems. The downloads and changelog are in the normal places. I’m not going to lie, I expected this release to happen really quickly, as VirtualBox 7.0 gave me a number of headaches. Hot on the heels of VirtualBox 7.0, we now have VirtualBox 7.0.2.