VirtualBox Upgrade to 6.1.2 on Feb 6, 2020.

We are planning to push out an update to Virtualbox. Those of you with “saved” or “paused” virtualbox VM’s will need to shut them down before applying the update, or else risk that those “saved” and “paused” VM’s won’t operate after the update. This is try of most updates to VirtualBox, but we thought it prudent to give our users a little warning.

The update is necessary as the current version of Virtualbox’s kernel modules will not build on kernels newer than 5.3.

Here is the release notes from our Package Repo Manager Tim.

VirtualBox in MX-19 Main will be upgraded to version 6.1.2 tomorrow, 2/6/2020. There have been a number of bugfixes and improvements since the current version, and the current version will not build its modules on the new 5.4+ version kernels so this update is necessary,

VirtualBox users need to know that any Saved or Paused VMs will not open after a VirtualBox version update. Here are your options to avoid trouble:
1) Shutdown the OS in any VMs you have before you upgrade.
2) Lock your current VirtualBox version so it won’t upgrade.[code]sudo apt-mark hold virtualbox*[/code]If you also do updates with Synaptic you will need to lock the virtualbox packages there as well since it ignores [i]apt-mark hold[/i] and apt-get ignores Synaptic’s package locks.

If you have already upgraded you have two options to repair.
A) If the saved state of the VM is not important to you, you can use the Discard Saved State… option in the settings for that VM and it should start up.
B) If the saved state is important you can reinstall your old Virtualbox packages from /var/cache/apt/archives, then follow 1) or 2) above.

7 thoughts on “VirtualBox Upgrade to 6.1.2 on Feb 6, 2020.”

  1. thank-you kindly,
    i already have 1 VM (XP), though it is shut down atm,
    & will shortly be adding a few more (Hurd, ReactOS, w7 & w10).
    this kind of heads-up for your users is much appreciated, in case we aren’t aware of potential issues.

  2. I have removed and reinstalled virtualbox using the apt command.
    I can not start a newly created vm?
    Any thoughts?

    $ sudo VirtualBox list vms
    WARNING: The character device /dev/vboxdrv does not exist.
    Please install the virtualbox-dkms package and the appropriate
    headers, most likely linux-headers-amd64.

    You will not be able to start VMs until this problem is fixed.
    Qt FATAL: QXcbConnection: Could not connect to display

      En mi particion de disco tengo 1/2 y 1/2 AMD /CMD
      Por lo tanto en el sector de amd tengo 22 Maquinas y sus respectivos Sistemas Operacionales, en muchos años no he tenido ningun problema , solo analizo y comprendo los libros para esta hermosa cibernetica.- Estudy in Private ,,,HACKLAT hacker latino.-

  3. cc1: some warnings being treated as errors
    make[2]: *** [scripts/ /var/lib/dkms/virtualbox-guest/6.1.2/build/vboxguest/combined-os-specific.o] Error 1
    make[1]: *** [scripts/ /var/lib/dkms/virtualbox-guest/6.1.2/build/vboxguest] Error 2
    make: *** [Makefile:1697: /var/lib/dkms/virtualbox-guest/6.1.2/build] Error 2

  4. What is up with 32 bit on 19? Synaptic says that Virtualbox is installed, however it does not appear anywhere, like accessories for example. I found that I should install virtualbox-q, but that is not to be found either.


Leave a Comment

MX Linux