Test for Virtualbox 6.0 (or 6.1) compatibility

[ottok]

Oracle did not kill Virtualbox and look and behold a version 6.0 has been released. Our project and Vagrantfile should be tested for Virtualbox 6.0 compatibility, with at least updates in documentation (https://seravo.com/docs/development/how-to-install/#windows-cygwin) and perhaps also some tweaks in the Vagrantfile.

[l3ku]

I have been using Virtualbox 6.x.x on OS X since almost immediately after it was released, and there have been no issues due to Virtualbox with our Vagrant box. We should also probably look into testing on Windows with Virtualbox 6.

[l3ku]

There is however this warning when starting the vagrant environment:

  wordpress-box: The guest additions on this VM do not match the installed version of
    wordpress-box: VirtualBox! In most cases this is fine, but in rare cases it can
    wordpress-box: prevent things such as shared folders from working properly. If you see
    wordpress-box: shared folder errors, please make sure the guest additions within the
    wordpress-box: virtual machine match the version of VirtualBox you have installed on
    wordpress-box: your host and reload your VM.
    wordpress-box:
    wordpress-box: Guest Additions Version: 5.2.18
    wordpress-box: VirtualBox Version: 6.0

This could cause some problems.

[l3ku]

I have been using Virtualbox 6.x.x on OS X since almost immediately after it was released, and there have been no issues due to Virtualbox with our Vagrant box. We should also probably look into testing on Windows with Virtualbox 6.

Windows tests also went OK. Other than the guest additions version, no other issues have come to my attention.

[ottok]

@JoosuaKoskinen Did you have some input here? Have you tested Virtualbox 6.1 or later, do they work well? Are they tested on both Windows, Mac and Linux?

Ubuntu 20.04 LTS ships with Virtualbox 6.1 so we should start testing and supporting the use of Virtualbox 6.1 now.

[JoosuaKoskinen]

I didn't notice this before making https://github.com/Seravo/docs/issues/39. I've tested Virtualbox 6.1 and Vagrant 2.2.9 (>= 2.2.7 should be enough) together on Linux and they did work well. The Vagrant file didn't work at first but that got fixed by downloading the latest one from this repo. I'll do a Windows test now.

[JoosuaKoskinen]

On Windows Virtualbox kept freezing during the boot process. I got it fixed by decreasing the amount of CPUs from 2 to 1. I'm not sure why that is, on Linux it works fine with multiple CPUs.

[Moppa5]

I tested our wordpress/beta Vagrant on Windows 10, 2004 version with Vagrant 2.2.9 and VirtualBox 6.1.2 installed using PowerShell guide. Vagrant up worked normally, wp-test went alright, s-test-commands returned no error on executed commands but rather returned some Python side error related to Seravo Plugin.

[ottok]

On Windows Virtualbox kept freezing during the boot process. I got it fixed by decreasing the amount of CPUs from 2 to 1. I'm not sure why that is, on Linux it works fine with multiple CPUs.

@JoosuaKoskinen Can you find some Vagrant/VirtualBox documentation about this, why did that phenomenon happen? Should we change in the Vagrantfile that all users always run with a single CPU? At https://www.vagrantup.com/docs/installation multiple hypervisors is mentioned but that is a different thing from multicore or multiple CPUs. On https://www.virtualbox.org/manual/UserManual.html there are no notes that jump in my eye.

Maybe something noteworthy in https://github.com/hashicorp/vagrant/blob/master/CHANGELOG.md or https://www.virtualbox.org/wiki/Changelog-6.1 ?

[wuppious]

Chiming in, Arch Linux running vagrant 2.2.9 and virtualbox 6.1.10, cannot give this box more than 1 CPU or the machine hangs on boot.

Does not happen with a minimal/trusty64 box I had lying around, I can give it 2 just fine.

[oxyc]

Switching to 1 CPU fixed issues on macos:

$ vboxmanage --version
6.1.12r139181

$ vagrant --version
Vagrant 2.2.9

$ sw_vers -productVersion
10.15.6

[oxyc]

Relevant issues where this was changed to 1 core in other projects:

https://github.com/geerlingguy/drupal-vm/issues/855 https://github.com/roots/trellis/issues/410

[TommiContursi]

I can also confirm that I managed to get this up and run with the beta box and only one core.

$ vagrant --version
Vagrant 2.2.13
$ vboxmanage --version
6.1.16r140961
$ sw_vers -productVersion
11.0.1

It's good to note that the latest macOS version, Big Sur is not compatible with VirtualBox 5.2 and most likely will never be. Even installing Virtualbox 6.1 was very difficult with the latest OS. That why it's important to research more on Virtualbox6.1 compatibility and not just rely on using version 5.2

[ottok]

Thanks @TommiContursi for the additional info! We are working on this.

[ottok]

A new Vagrant box version has been released today: https://app.vagrantup.com/seravo/boxes/wordpress/versions/20201127.0.0

It fixes some known 6.1 compatibility issues, but we need more feedback to iron out the remaining compatibility issues. Feedback and experiences welcome! :)

[ottok]

A new Vagrant box version has been released: https://app.vagrantup.com/seravo/boxes/wordpress/versions/20201205.0.0

It should work with VirtualBox 6.1 everywhere. Please test and report here :)

[ottok]

We have not got any new reports about VirtualBox 6.x not working, so the latest release did indeed fix all known compatibility issues. Closing.