Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - virtualbox-bin

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: virtualbox-bin 5.1.14-1

Git Clone URL: https://aur-dev.archlinux.org/virtualbox-bin.git (read-only)
Package Base: virtualbox-bin
Description: Oracle VM VirtualBox Binary Edition (Oracle branded non-OSE version)
Upstream URL: http://virtualbox.org/
Keywords: virtualbox
Licenses: GPL2
Conflicts: virtualbox, virtualbox-host-dkms, virtualbox-host-modules-arch
Provides: virtualbox=5.1.14
Replaces: virtualbox-sun, virtualbox_bin
Submitter: Rainmaker
Maintainer: Rainmaker
Last Packager: Rainmaker
Votes: 34
Popularity: 2.528863
First Submitted: 2015-08-18 09:16
Last Updated: 2017-01-17 12:35

Required by (13)

Sources (7)

Latest Comments

1 2 Next › Last »

dkadioglu commented on 2017-01-19 12:44

Maybe you can integrate vboxreload from the Arch package: https://git.archlinux.org/svntogit/community.git/tree/trunk/vboxreload?h=packages/virtualbox
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.

chrko commented on 2016-08-22 08:00

The conflicts are wrong. The host modules have been renamed?

Rainmaker commented on 2016-04-03 21:23

Thank you for the patch k0ste.

k0ste commented on 2016-04-03 10:30

This patch fix:
- Modules now build;
- Modules build via ALPM hook;
- Load all vbox modules (because we need network);
- modules-load.d in /usr, not /etc (etc for users, usr for packages);


Rainmaker commented on 2016-03-22 14:48

Could you check whether there is a "dkms.conf" file in /var/lib/dkms/vboxhost/5.0.16/source/?

This directory should be a symlink to /opt/VirtualBox/src/vboxhost

It is done at the very end of the PKGBUILD:

# Register into DKMS
install -dm 755 "$pkgdir/var/lib/dkms/vboxhost/$pkgver"
ln -s '/opt/VirtualBox/src/vboxhost' "$pkgdir/var/lib/dkms/vboxhost/$pkgver/source"

Bitl0rd commented on 2016-03-22 13:52

dkms autoinstall:
Error! Could not locate dkms.conf file.
File: does not exist.

Rainmaker commented on 2015-11-23 12:58

The package automatically registers itself with DKMS.

A simple "dkms autoinstall" probably would have sufficed.

The package warns for this during post_install:

cat <<EOF

==> Remember to add allowed users to the vboxusers group:
==> # gpasswd -a USERNAME vboxusers
==> To compile/load virtualbox modules automatically at startup you can add dkms in your DAEMONS
==> To build and install your modules run dkms autoinstall

(in contrast with my earlier comment, the package has always done this)