Package Details: virtualbox-bin 5.1.28-1

Git Clone URL: (read-only)
Package Base: virtualbox-bin
Description: Oracle VM VirtualBox Binary Edition (Oracle branded non-OSE version)
Upstream URL:
Keywords: virtualbox
Licenses: GPL2
Conflicts: virtualbox, virtualbox-host-dkms, virtualbox-host-modules-arch
Provides: virtualbox=5.1.28
Replaces: virtualbox-sun, virtualbox_bin
Submitter: Rainmaker
Maintainer: gary9872
Last Packager: gary9872
Votes: 40
Popularity: 1.231221
First Submitted: 2015-08-18 09:16
Last Updated: 2017-09-29 00:31

Required by (21)

Sources (7)

Latest Comments

Ralf_Mardorf commented on 2017-10-14 06:55


when virtualbox-bin was orphaned, I build 5.1.28 due to a lack of time from an incomplete edited 5.1.26 snapshot.
Today I used your snapshot for 5.1.28, I only edited the "pkgrel" entry.
Your snapshot suffers from the same issue as mine.

[rocketmouse@archlinux ~]$ sudo pacman -S linux linux-headers
(1/3) Install DKMS modules
==> dkms install virtualbox/bin -k 4.13.5-1-ARCH
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
Error! Bad conf file.
File: /usr/src/virtualbox-bin/dkms.conf
does not represent a valid dkms.conf file.
[rocketmouse@archlinux ~]$ grep virtualbox-bin /var/log/pacman.log | grep upgraded | tail -2
[2017-09-17 20:34] [ALPM] upgraded virtualbox-bin (5.1.26-1 -> 5.1.28-1)
[2017-10-14 08:38] [ALPM] upgraded virtualbox-bin (5.1.28-1 -> 5.1.28-2)


mOGLie commented on 2017-10-01 16:58

I tried to adapt this packages for VBox 5.2.0_*.
5.2.0_BETA2 works fine for me. 5.2.0_BETA3 and 5.2.0_RC1 were runing into trouble with the Kernel modules.

I have copied the Makefile from BETA2 to RC1 and it work.
I don't know what I have done, but it works.

dtschmitz commented on 2017-09-29 15:59

On behalf of the entire AUR community, 'THANK YOU' for adopting this package.

Kindest Regards,
Dietrich T. Schmitz

dtschmitz commented on 2017-07-19 17:40

Thanks for maintaining this package for Arch.
I have an error:
RTR3InitEx failed with rc=-1912 (rc=-1912)

The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing


may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.

where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

I have done everything I can think of, uninstall everything; reinstall everything; jump down, spin around, pick up a bail of cotton; wax on/wax off, to no avail.

Can you help?
Thank you. -- Dietrich

avkonarev commented on 2017-06-12 18:48

Please, transfer "linux-headers" to the list of "makedepends=". I'm using the kernel "linux-lts" , and I do not need this package at all. I think this situation is for many. Thank you.

shillshocked commented on 2017-04-25 15:25

Just so you know, virtualbox 5.1.20 isn't working for me. It killed my virtualbox ALSA audio and made it NULL audio. Going back to 5.1.18-2 fixed it.

dkadioglu commented on 2017-01-19 12:44

Maybe you can integrate vboxreload from the Arch package:
Would that be possible?

Regarding the Extension pack my idea was not to directly integrate the extpack into the PKGBUILD but, to not delete the already installed one on every upgrade of virtualbox-bin. An example:
1. Install virtualbox-bin in version 5.1.12
2. Download the appropriate extension pack from the Oracle website
3. Install the extension pack
4. Install virtualbox-bin in version 5.1.14
At the moment during the upgrade the extension pack installed in step 3 has been deleted so I have to do step 2 and 3 again. What I'm proposing is to not delete the extension pack from step 2 which should lead to an update dialog for the extension pack the next time when Virtualbox is started. If I confirm that dialog the new extension pack is downloaded and installed automatically - this is the case with the official Arch package at least.
I hope it is a bit more clear now.

Rainmaker commented on 2017-01-19 12:01

"vboxreload" does not seem to be present in the current release. At least, I cannot find any executable by that name.

Integrating the extension is possible, but not done on purpose. As there is a separate license for the extension pack, not all users may automatically want this.

You can install vbox-ext-oracle from AUR if you want it. Unfortunately, despite repeated requests, I am not a (co-)maintainer of that package, so am unable to keep these two packages in sync.

dkadioglu commented on 2017-01-18 06:31

Would it be possible to do the following:

1. Integrate the vboxreload command
2. Keep the already installed VBox Extension Module (then the update mechanism should kick in as it does in the Arch package)

Thanks, also for taking care of the AUR packagage!

Rainmaker commented on 2016-08-30 11:15

Good catch. Also, virtualbox-ose no longer exists.

I've altered it locally, but don't feel this justifies a new release. I'll stage the change, but will push it when the next virtualbox version is released.

All comments