Package Details: virtualbox-bin 6.1.14-3

Git Clone URL: (read-only, click to copy)
Package Base: virtualbox-bin
Description: Powerful x86 virtualization for enterprise as well as home use (Oracle branded non-OSE)
Upstream URL:
Keywords: machine oracle virtualization vm
Licenses: GPL2
Conflicts: virtualbox, virtualbox-host-dkms, virtualbox-host-modules-arch
Provides: VIRTUALBOX-HOST-MODULES, virtualbox=6.1.14, virtualbox-host-dkms
Replaces: virtualbox-sun, virtualbox_bin
Submitter: Rainmaker
Maintainer: dbermond
Last Packager: dbermond
Votes: 56
Popularity: 1.37
First Submitted: 2015-08-18 09:16
Last Updated: 2020-10-18 01:05

Required by (32)

Sources (13)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

dbermond commented on 2020-10-19 03:22

@drankinatty I have an impression that you did not read my previous comment. I'll repeat it one more time: there is no guest additions source to patch here because this is a -bin (pre-compiled) package. There is only dkms sources to patch on this package. And there is nothing being patched on '/tmp' here.

drankinatty commented on 2020-10-19 02:37

If you are just repackaging what is built in virtualbox-bin-guest-iso-6.1.14-3-any.pkg.tar.zst that is provided as part of this package, then it's Oracle's issue. The problem is -- while you patch /tmp/vbox.0/r0drv/linux/the-linux-kernel.h to build this package -- the src files installed from virtualbox-bin-guest-iso-6.1.14-3-any.pkg.tar.zst to the guest when you install the guest-additions are not patched. So is there away to patch the same files you patch to build the host modules (with the same patch) so they are packaged in the virtualbox-bin-guest-iso-6.1.14-3 built by this package so that guest-additions build?

dbermond commented on 2020-10-18 13:31

@drankinatty What are you talking about? This is a -bin package and the guest additions are not built from sources. There is no guest additions source to patch here and the package does not install a directory named '/opt/VBoxGuestAdditions-6.1.14/'.

drankinatty commented on 2020-10-18 10:26

Linux 5.9-1 guest-additions build fails so it looks like applying the same patch is needed by the guest-additions package. Error from vboxadd-setup.log

In file included from /tmp/vbox.0/VBoxGuest-linux.c:36:
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:141:11: fatal error: linux/smp_lock.h: No such file or directory
  141 | # include <linux/smp_lock.h>
      |           ^~~~~~~~~~~~~~~~~~
compilation terminated.

The 021-kernel-5.9.patch looks like it should have addressed this, maybe this can be adapted to the guest-additions package produced during the build?

The crux is this, the src file installed on the host in /usr/src/vboxhost-6.1.14_non_OSE/ are patched for 5.9.1, the files that get installed on the guest to /opt/VBoxGuestAdditions-6.1.14/src/vboxgues-6.1.14/ are not (they are still dated Sept. 4, 2020). So guest additions fail to build on Arch guests.

dbermond commented on 2020-09-05 14:52

@Kr1ss Thanks for pointing this. Fixed.

firewalker commented on 2020-08-17 09:02

Unfortunately in my case the versions that works causes kernel panics.

firewalker commented on 2020-08-17 08:37

Those versions work:

dbermond commented on 2020-08-14 13:06

@nursoda At the time of this writing, VirtualBox 6.1.13 is not yet released by upstream. Not even the repository package is updated to 6.1.13.

nursoda commented on 2020-08-14 13:01

For the time being, could you please update to 6.1.13 – virtualbox-ext-oracle is updated already and breaks virtualbox-bin due to 12 vs 13 version mismatch. I know that I can downgrade that but … I try to stay up-to-date on all packages ;) Anyway: Does 6.1.13 solve the Kernel 5.8 issue?

dbermond commented on 2020-08-12 20:25

Upgrading linux to 5.8 will break virtualbox-bin 6.1.12.

I've prepared a patch for linux 5.8 (based on the repository package) but apparently it modifies the modules version, since it causes a 'module version mismatch' error when running a virtual machine.

So a patch for the dkms sources will not be sufficient. We need an update from upstream supporting linux 5.8. Based on the release history, it should not take too much long.