Package Details: virtualbox-bin 5.2.0-1

Git Clone URL: https://aur.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.2.0
Replaces: virtualbox-sun, virtualbox_bin
Submitter: Rainmaker
Maintainer: gary9872
Last Packager: gary9872
Votes: 41
Popularity: 1.388607
First Submitted: 2015-08-18 09:16
Last Updated: 2017-11-03 23:22

Required by (20)

Sources (8)

Pinned Comments

drankinatty commented on 2017-11-10 05:58

Note, on upgrade from 5.1.28 to 5.2, dkms does not handle previous module unload as all upgrades between 5.1.2X have and following upgrade there is module and virtualbox version mismatch. Further, headless Windows clients accessed remotely can not receive keyboard or mouse input (regadless of host-key use) as there is an evident incompatibility between the 5.1.2X guest additions and the new 5.2 additions. Reported with Oracle ticket/17259. Just be aware after host upgrade to 5.2, if you have remote clients accessing headless windows guests, there is a high likelihood they will not be able to access the guest until guest additions are manually updated to 5.2 on the host machine (remote clients can no longer login and update guest additions as normal)

gary9872 commented on 2017-11-04 18:35

Bumped to 5.2.0

Dkms issue should be fixed now. Special thanks to Christian Hesse for some patching.

Latest Comments

gary9872 commented on 2017-11-22 00:06

Ralf

I don't use the testing repos.

If someone does and would like to submit a patch, I'd be happy to add it.

Ralf_Mardorf commented on 2017-11-19 21:27

My apologies for not posting the output elsewhere and just posting a link here.

virtualbox-bin-5.2.0-1 was build from your tarball. I only looked at the OSE version for comparison. As already pointed out, despite the messages the modules were build, at least for kernel versions < 4.14.0. Bevor I rebuild the package from your tarball, I reinstalled the already build package. The link always is against /usr/src/virtualbox-bin. Even after fixing the link, the modules for 4.14.0 from testing were not build.

[rocketmouse@archlinux current]$ sudo pacman -U virtualbox-bin-5.2.0-1-x86_64.pkg.tar.xz
[snip]
warning: virtualbox-bin-5.2.0-1 is up to date -- reinstalling
[snip]
warning: directory permissions differ on /usr/src/
filesystem: 775 package: 755

==> Remember to add allowed users to the vboxusers group:
==> # gpasswd -a USERNAME vboxusers
:: Running post-transaction hooks...
(1/5) Install DKMS modules
==> dkms install vboxhost/5.2.0 -k 4.13.13-rt5-1-rt
==> dkms install vboxhost/5.2.0 -k 4.14.0-2-ARCH
Error! Bad return status for module build on kernel: 4.14.0-2-ARCH (x86_64)
Consult /var/lib/dkms/vboxhost/5.2.0/build/make.log for more information.
==> dkms install vboxhost/5.2.0 -k 4.11.12-rt16-1-rt-cornflower
==> dkms install vboxhost/5.2.0 -k 4.14.0-rt1-1-rt-pussytoes
Error! Bad return status for module build on kernel: 4.14.0-rt1-1-rt-pussytoes (x86_64)
Consult /var/lib/dkms/vboxhost/5.2.0/build/make.log for more information.
(2/5) Updating icon theme caches...
(3/5) Arming ConditionNeedsUpdate...
(4/5) Updating the desktop file MIME type cache...
(5/5) Updating the MIME type database...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'

[rocketmouse@archlinux current]$ ls -hAl /var/lib/dkms/virtualbox/
total 4.0K
drwxr-xr-x 3 root root 4.0K Nov 19 17:41 bin
[rocketmouse@archlinux current]$ ls -hAl /var/lib/dkms/virtualbox/bin/
total 4.0K
drwxr-xr-x 3 rocketmouse rocketmouse 4.0K Nov 19 17:42 build
lrwxrwxrwx 1 root root 23 Nov 14 09:34 source -> /usr/src/virtualbox-bin
[rocketmouse@archlinux current]$ ls -hAld /usr/src/v*
drwxr-xr-x 6 root root 4.0K Nov 19 21:16 /usr/src/vboxhost-5.2.0
drwxr-xr-x 2 rocketmouse rocketmouse 4.0K Sep 17 20:40 /usr/src/virtualbox-bin

[rocketmouse@archlinux tmp]$ wget -q https://aur.archlinux.org/cgit/aur.git/snapshot/virtualbox-bin.tar.gz
[rocketmouse@archlinux tmp]$ tar xf virtualbox-bin.tar.gz
[rocketmouse@archlinux tmp]$ cd virtualbox-bin/
[rocketmouse@archlinux virtualbox-bin]$ cp -ai PKGBUILD PKGBUILD~
[rocketmouse@archlinux virtualbox-bin]$ nano PKGBUILD
[rocketmouse@archlinux virtualbox-bin]$ diff PKGBUILD PKGBUILD~
8c8
< pkgrel=2
---
> pkgrel=1
[rocketmouse@archlinux virtualbox-bin]$ makepkg -s
[snip]
==> Finished making: virtualbox-bin 5.2.0-2 (Sun Nov 19 21:52:04 CET 2017)
[rocketmouse@archlinux virtualbox-bin]$ sudo pacman -U virtualbox-bin-5.2.0-2-x86_64.pkg.tar.xz
[snip]
:: Processing package changes...
(1/1) upgrading virtualbox-bin [snip] 100%
warning: directory permissions differ on /usr/src/
filesystem: 775 package: 755

==> Remember to add allowed users to the vboxusers group:
==> # gpasswd -a USERNAME vboxusers
:: Running post-transaction hooks...
(1/5) Install DKMS modules
==> dkms install vboxhost/5.2.0 -k 4.13.13-rt5-1-rt
==> dkms install vboxhost/5.2.0 -k 4.14.0-2-ARCH
Error! Bad return status for module build on kernel: 4.14.0-2-ARCH (x86_64)
Consult /var/lib/dkms/vboxhost/5.2.0/build/make.log for more information.
==> dkms install vboxhost/5.2.0 -k 4.11.12-rt16-1-rt-cornflower
==> dkms install vboxhost/5.2.0 -k 4.14.0-rt1-1-rt-pussytoes
Error! Bad return status for module build on kernel: 4.14.0-rt1-1-rt-pussytoes (x86_64)
Consult /var/lib/dkms/vboxhost/5.2.0/build/make.log for more information.
(2/5) Updating icon theme caches...
(3/5) Arming ConditionNeedsUpdate...
(4/5) Updating the desktop file MIME type cache...
(5/5) Updating the MIME type database...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'

[rocketmouse@archlinux virtualbox-bin]$ ls -hAl /var/lib/dkms/virtualbox/
total 4.0K
drwxr-xr-x 3 root root 4.0K Nov 19 17:41 bin
[rocketmouse@archlinux virtualbox-bin]$ ls -hAl /var/lib/dkms/virtualbox/bin/
total 4.0K
drwxr-xr-x 3 rocketmouse rocketmouse 4.0K Nov 19 17:42 build
lrwxrwxrwx 1 root root 23 Nov 14 09:34 source -> /usr/src/virtualbox-bin
[rocketmouse@archlinux virtualbox-bin]$ ls -hAld /usr/src/v*
drwxr-xr-x 6 root root 4.0K Nov 19 21:54 /usr/src/vboxhost-5.2.0
drwxr-xr-x 2 rocketmouse rocketmouse 4.0K Sep 17 20:40 /usr/src/virtualbox-bin

JFTR

[rocketmouse@archlinux virtualbox-bin]$ ls -hAld /usr/src/
drwxrwxr-x 43 root rocketmouse 4.0K Nov 18 08:00 /usr/src/

Fixing the link

[rocketmouse@archlinux virtualbox-bin]$ sudo unlink /var/lib/dkms/virtualbox/bin/source
[sudo] password for rocketmouse:
[rocketmouse@archlinux virtualbox-bin]$ sudo ln -s /usr/src/vboxhost-5.2.0 /var/lib/dkms/virtualbox/bin/source
[rocketmouse@archlinux virtualbox-bin]$ ls -hAl /var/lib/dkms/virtualbox/bin/
total 4.0K
drwxr-xr-x 3 rocketmouse rocketmouse 4.0K Nov 19 17:42 build
lrwxrwxrwx 1 root root 23 Nov 19 22:05 source -> /usr/src/vboxhost-5.2.0

4.14.0-2-ARCH is from testing, but my Arch install is an up to date install with testing commented out.

[rocketmouse@archlinux virtualbox-bin]$ sudo dkms install vboxhost/5.2.0 -k 4.14.0-2-ARCH

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area...
make -j2 KERNELRELEASE=4.14.0-2-ARCH -C /usr/lib/modules/4.14.0-2-ARCH/build M=/var/lib/dkms/vboxhost/5.2.0/build..........(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.14.0-2-ARCH (x86_64)
Consult /var/lib/dkms/vboxhost/5.2.0/build/make.log for more information.

[rocketmouse@archlinux virtualbox-bin]$ grep "testing]" -A3 /etc/pacman.conf
#[testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist

--
#[community-testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist

--
#[multilib-testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist

[rocketmouse@archlinux virtualbox-bin]$ grep -i error /var/lib/dkms/vboxhost/5.2.0/build/make.log
/var/lib/dkms/vboxhost/5.2.0/build/vboxnetflt/linux/VBoxNetFlt-linux.c:741:24: error: ‘SKB_GSO_UDP’ undeclared (first use in this function); did you mean ‘SKB_GSO_ESP’?
/var/lib/dkms/vboxhost/5.2.0/build/vboxnetflt/linux/VBoxNetFlt-linux.c:1276:53: error: ‘SKB_GSO_UDP’ undeclared (first use in this function); did you mean ‘SKB_GSO_ESP’?
/var/lib/dkms/vboxhost/5.2.0/build/vboxnetflt/linux/VBoxNetFlt-linux.c:1526:47: error: ‘SKB_GSO_UDP’ undeclared (first use in this function); did you mean ‘SKB_GSO_ESP’?
make[2]: *** [scripts/Makefile.build:314: /var/lib/dkms/vboxhost/5.2.0/build/vboxnetflt/linux/VBoxNetFlt-linux.o] Error 1
make[1]: *** [scripts/Makefile.build:573: /var/lib/dkms/vboxhost/5.2.0/build/vboxnetflt] Error 2
make: *** [Makefile:1503: _module_/var/lib/dkms/vboxhost/5.2.0/build] Error 2

gary9872 commented on 2017-11-15 02:31

Ralf, I had another DKMS issue, which should be fixed The one you are mentioning is different.

I'm trying to replicate your issue.

Pacman -S linux-header gives:

[snip]
(1/3) Install DKMS modules
==> dkms install nvidia/387.22 -k 4.13.11-1-ARCH
==> dkms install vboxhost/5.2.0 -k 4.13.11-1-ARCH
(2/3) Updating linux initcpios
[snip]
(no errors)

asp checkout virtualbox <--- I don't maintain this version.(OSE/community)


The dkms module should be vboxhost rather than virtualbox you seem to have

and should look something like this

rwxrwxrwx 1 root root 23 Nov 14 21:25 source -> /usr/src/vboxhost-5.2.0
drwxr-xr-x 3 root root 4096 Nov 14 21:26 4.13.11-1-ARCH


Ralf_Mardorf commented on 2017-11-14 08:37

$ sudo rm -Ir /var/lib/dkms/virtualbox/bin/
rm: remove 1 argument recursively? y
$ sudo rm -Ir /var/lib/dkms/virtualbox/bin/
rm: remove 1 argument recursively? y
rm: cannot remove '/var/lib/dkms/virtualbox/bin/': No such file or directory
$ sudo pacman -S linux{,-docs,-headers}
[snip]
$ ls -hAl /var/lib/dkms/virtualbox/bin/
total 4.0K
drwxr-xr-x 3 rocketmouse rocketmouse 4.0K Nov 14 09:34 build
lrwxrwxrwx 1 root root 23 Nov 14 09:34 source -> /usr/src/virtualbox-bin

Ralf_Mardorf commented on 2017-11-14 08:19

Remember, the flaw doesn't affect building the modules, they are located in /lib/modules/*/kernel/misc/.
I'm short in time, so I only did a short test:

$ asp update
[snip]
$ asp checkout virtualbox
Cloning into '/tmp/virtualbox'...
done.
$ grep VER virtualbox/trunk/virtualbox-host-dkms.conf
PACKAGE_VERSION=@VERSION@_OSE
$ grep VER /usr/src/virtualbox-bin/dkms.conf
PACKAGE_VERSION=
$ nano /usr/src/virtualbox-bin/dkms.conf
$ grep VER /usr/src/virtualbox-bin/dkms.conf
PACKAGE_VERSION=5.2.0
$ sudo pacman -S linux{,-docs,-headers}
[snip]
:: Running post-transaction hooks...
(1/3) Install DKMS modules
==> dkms install vboxhost/5.2.0 -k 4.13.12-1-ARCH
==> dkms install virtualbox/bin -k 4.13.12-1-ARCH
Error! Bad return status for module build on kernel: 4.13.12-1-ARCH (x86_64)
Consult /var/lib/dkms/virtualbox/bin/build/make.log for more information.
[snip]

Ralf_Mardorf commented on 2017-11-14 06:32

# pacman -S linux linux-headers
[snip]
Packages (2) linux-4.13.12-1 linux-headers-4.13.12-1
[snip]
:: Running post-transaction hooks...
(1/3) Install DKMS modules
==> dkms install vboxhost/5.2.0 -k 4.13.12-1-ARCH
==> dkms install virtualbox/bin -k 4.13.12-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.
[snip]
$ pacman -Q virtualbox-bin
virtualbox-bin 5.2.0-1

drankinatty commented on 2017-11-10 05:58

Note, on upgrade from 5.1.28 to 5.2, dkms does not handle previous module unload as all upgrades between 5.1.2X have and following upgrade there is module and virtualbox version mismatch. Further, headless Windows clients accessed remotely can not receive keyboard or mouse input (regadless of host-key use) as there is an evident incompatibility between the 5.1.2X guest additions and the new 5.2 additions. Reported with Oracle ticket/17259. Just be aware after host upgrade to 5.2, if you have remote clients accessing headless windows guests, there is a high likelihood they will not be able to access the guest until guest additions are manually updated to 5.2 on the host machine (remote clients can no longer login and update guest additions as normal)

gary9872 commented on 2017-11-04 18:35

Bumped to 5.2.0

Dkms issue should be fixed now. Special thanks to Christian Hesse for some patching.

Ralf_Mardorf commented on 2017-10-14 06:55

Hi,

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
[snip]
(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.
[snip]
[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)

Regards,
Ralf

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

Gary,
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

Hello,
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

'/sbin/vboxconfig'

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: 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?
virtualbox-host-dkms
virtualbox-host-modules-arch

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);

https://k0ste.ru/zerobin/?27beb28fb95448a5#ryV+6o+81n6FFA5Z3PeGSX5nNvOEL6m8IrXHPhmK1zA=

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

@the9ull:
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
EOF

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

the9ull commented on 2015-11-21 15:56

Hello,

with this package I had to build the kernel module myself, and no instuctions are provided by the isntall script.

I runned:

# cd /opt/VirtualBox/src/vboxhost/vboxdrv
# make && make install
# gpasswd -a USER vboxusers

I relogged and all worked.

Bastard commented on 2015-10-03 11:53

pkgver=5.0.6
_build=103037

md5 9d67e2df72630dc2ac5983c7cdb1cf5f

Worked like a charm again.

Rainmaker commented on 2015-09-09 18:53

I am currently on holiday, and it'll be another 2 weeks before I have access to my laptop / ssh key.

Let me know who I can make a (temporary) co maintainer to push this update.

Bastard commented on 2015-09-09 10:39

Thanks for making this package. I tested with the updates below and had no issues.

pkgver=5.0.4
_build=102546

md5 8028829331bc0822fa2d2d3cf301dda3