Oracle VirtualBox 7.0.10
VirtualBox 7.0.10 was released a few days ago and I finally got round to trying it.
I’ve installed it on my Windows 10 and 11 machines with no drama. For the previous release I had some issues with Windows 10. I had to uninstall then reinstall it to get it to work. For this release a straight upgrade was fine on both Windows versions.
At the same time I noticed Vagrant 2.3.7 had been released. All my test systems are built with Vagrant, so I grabbed it before testing my builds with the new version of VirtualBox.
If you are new to Vagrant and want to learn, you might find this useful.
Once you understand that, I found the best way of learning more was to look at builds done by other people. You can see all my Vagrant builds here.
I’ve already updated the relevant builds to include the latest versions of OpenJDK, Tomcat, ORDS and SQLcl. I’ll go through and add the latest round of Oracle database patches where necessary over the next few days.
With each new release of VirtualBox I rebuild my Vagrant boxes (Oracle Linux 7, 8 and 9) so they have the latest guest additions. These Vagrant boxes are the base for all my Vagrant builds. The boxes are built using Packer. I had a quick check and noticed Packer 1.9.2 was available, so I picked that up before starting my builds. The new version of the boxes can be seen here.
If you are interested in creating your own Packer builds, you might take inspiration from mine, available here.
How did it all go?
The new version of Packer worked fine with the new version of VirtualBox, and my boxes were built and uploaded in no time.
From there, all the Vagrant builds I’ve tried worked with no hiccups, so all versions seem to be playing well with each other.
I’ll be doing lots of testing over the next few days. I’ll update here if I notice anything unusual.
What about the VirtualBox GUI?
In the past people have asked me about issues they have had with the VirtualBox GUI after a new release, and my answer has always been the same. I don’t use it. I use Vagrant. As a result, when I say VitualBox is working fine I am never commenting on the GUI side of VirtualBox. For all I know it could be a disaster, but it wouldn’t affect me. I just do “vagrant up” and wait while the magic happens… 🙂
If you want my advice, try using Vagrant and you will never want to do manual configuration in the GUI again!