Arch Linux User Repository

Hi, I needed to downgrade dkms from 3.0.2-1 to 3.0.1-1, see the aur-general Archives. Regards, Ralf

With Linux 5.15, for Linux Guests, vboxadd-setup.log will show:

error: no such file or directory # include <drm/drm_irq.h>

Since most of the features are native in the kernel, this build failure installing guest additions seems to only effect the initial modesetting for the terminal. X, Shared-Folders, and the rest continues to work fine on the guest. Notified Oracle via the Virtualbox list and we will see what they say. Current Oracle TestBuilds (revs: 148164 and 148140-ext pack) do not address the issue.

So at least for virtualbox-bin, the 5.15 update doesn't cause any significant issues (thankfully!)

@drankinatty :

https://aur.archlinux.org/cgit/aur.git/commit/?h=virtualbox-bin&id=b37833a5bc43761058a9dcc2f2ba28a692e110c9

6.1.28 is out -- just update the version number, build no, etc.. and sums and it is good to go.

Current virtualbox-bin package dated 2021-07-29 and showing version 6.1.26 r145957 also works fine on current kernel 5.14.2-arch1-2 for me.

Linux kernel 5.14 is supported by VirtualBox test builds 6.1.27r146191 and newer.

@drankinatty Thanks for appreciating the package. Working fine for me too.

Kudos on the fast update -- all working well.

@drankinatty There is no virtualbox-bin directory on the AUR sources.

Was inclusion of the ./virtualbox-bin directory in the source package intentional?

Well, the commit of "Add patch for linux 5.11" should do it. You were one step ahead. I just built from the teestbuild which incorporates the patch. (I am quite pleasantly surprised you already had it covered) Now if we can just get Oracle to fix the guest issue with 5.10+, we will be is great shape.

@drankinatty I have no problems building the virtualbox kernel modules with latest 5.11.1 kernel. Works fine for me.

Fun continues. vboxnetflt fails to build with 5.11. Bug: https://www.virtualbox.org/ticket/20198 The testbuilds https://www.virtualbox.org/wiki/Testbuilds as of revision 142917 allows 5.11 vboxnetflt module to build on Arch. However, Arch host/Arch Guest, Guest will fail to boot with Kernel Panic for kernels after 5.9. Bug is months old and still unresolved https://www.virtualbox.org/ticket/20055

6.1.18-1 bug can't select ISO file in KIO Open dialog is gone

Any luck with 6.1.18 that came out on 1/12/21? Note, I built from 6.1.18 and the Archlinux Host is fine. However, attempting to update the Archlinux guest to 5.10 succeeds in installing the Linux_Guest_Additions, but on reboot a Kernel Panic occurs. This has been an continual issue with Linux 5.10 guests. (make a snapshot before you try) Reverting the guest to Linux 5.9.14 and all is good.

See: https://www.virtualbox.org/ticket/20055

Virtualbox 6.1.16 : Storage Section under VM configuration : Can't select ISO file in KIO Open dialog [Was OK before release of 6.1.14]

https://bugs.mageia.org/show_bug.cgi?id=27433

@ElijahLynn This package is not the virtualbox extension pack. You can find the extension pack here. The package description already states what differentiates it from the repository one: "Oracle branded non-OSE".

Appreciate that @Kr1ss. I read that a bit and see it is basically the "VirtualBox Extension Pack" which according to https://www.nakivo.com/blog/how-to-install-virtualbox-extension-pack/, says:

• Support for USB 2.0 and USB 3.0 devices
• Host webcam pass-through
• VirtualBox Remote Desktop Protocol (VRDP)
• Disk image encryption with AES algorithm
• Intel PXE Boot ROM

Would be good if somehow this package could put that in a description of sorts to distinguish the two because as an outsider, I had no idea.

@ElijahLynn basically the package in [community] provides you the fully free and open source edition, while this one here is the Oracle branded one, containing some proprietary extensions. (See §1 in the licensing FAQ)

What is the difference between virtualbox-bin AUR and https://www.archlinux.org/packages/community/x86_64/virtualbox/?

Yes, thank you, after discussing on the vbox-users list, it was the binary.iso that contains the files that needed patching and there isn't any way for you to do that. Sorry for the noise -- also 6.1.16 is out and works fine with Linux 5.9.1 -- all you need to do is update the build no., drop the patch, set release to 1 and regen the checksums. (I hate kernel version updates....)

@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.

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?

@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/'.

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.

@Kr1ss Thanks for pointing this. Fixed.

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

Those versions work:

https://www.virtualbox.org/download/testcase/VirtualBox-6.1.97-139787-Linux_amd64.run

https://www.virtualbox.org/download/testcase/VirtualBoxSDK-6.1.97-139678.zip

https://www.virtualbox.org/download/testcase/Oracle_VM_VirtualBox_Extension_Pack-6.1.97-139662.vbox-extpack

@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.

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?

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.

Update: VirtualBox Ticket #19719

Hi, after installing 6.1.12-1 + extension pack a Windows 10 guest can be used with the new guest additions, but a Windows 7 guest doesn't boot anymore, after installing the guest additions. Starting Windows 7 in safe mode works, but doesn't find a solution. I restored Windows 7 from a snapshot and tried again. The Windows 7 guest failed to boot again after installing the guest additions. Does anybody experience the same issue?

@joerg-krause AUR helpers are not supported. Please use makepkg.

No malicious code on this PKGBUILD, it's just extracting the main source file.

The Aura package manager fails to build this package to avoid potentially malicious code:

sudo aura -Ax virtualbox-bin
aura >>= Determining dependencies...
aura >>= WARNING: The PKGBUILD of `virtualbox-bin` contains blacklisted bash expressions.

    sh "VirtualBox-${pkgver}-${_build}-Linux_amd64.run" --target "${pkgname}-${pkgver}" --nox11 --noexec

aura >>= `sh` can be used to execute arbitrary code not tracked by this PKGBUILD.
aura >>= Do you wish to quit the build process? [Y/n] 
aura >>= Cancelled further processing to avoid potentially malicious bash code.

Romario74, see the "Update" added to my original comment. I noticed that the extension pack needed to be reinstalled already before you replied. However, there's still an issue displayed for one guest's settings, even while the guest seems to be usable. After doing some further testing virtualbox-bin 6.1.4-2 seems not to work when booted to the real-time patched kernel 5.6.2, it seems to work when booted to the real-time patched kernel 4.19.106. "Seems", since I only made short tests and those failed when booted to the kernel 5.6.2, but worked when booted to the kernel 4.19.106. Now I'll try to backup two tablets with the Windows 7 and with the Windows 10 guest, while booted into 5.6.2-arch1-2 with "threadirqs". Until now the Windows 7 guest works. If I don't report anything else within the next hours, it continued to work without failure and the Windows 10 guest worked, too.

You have to reinstall the extension pack. This is what gives you USB support for your VMs. No need to restore from backup. And thanks for the virtualbox update, works fine with kernel 5.6.

A self-build real-time patched kernel 5.6.2-rt1 as well as 5.6.2-arch1-2 from Testing, with virtualbox-bin 6.1.4-2, trying to start a Windows 10 or Windows 7 guest fails with "Implementation of the USB 2.0 controller not found!" The same happens for a self-build real-time patched 4.19.106-rt46. After downgrading to virtualbox-bin 6.1.4-1, the self-build real-time patched kernel 4.19.106-rt46, that could be used before the upgrade to virtualbox-bin 6.1.4-2, still results in the same error. Even while I'm loading and unloading the modules on demand, I restarted the machine to no avail. FWIW all modules were build. The vbox and vbox-prev files do only contain different timestamps, anything else doesn't differ. The snapshots were not touched at all. Since it worked a few hours before I upgraded virtualbox-bin, nothing else was upgraded, I'll restore the guests from backups or what ever else might be broken.

Update: There was no need to restore from a backup, I just needed to reinstall the extension pack, so perhaps it even works with kernel 5.6. I can't test it now. Both Windows guests can be used again, but an invalid setting for the Windows 7 guest is detected, it's just not mentioned what setting.

@Romario74 I've added a patch for linux 5.6.

dkms modules do not build with kernel 5.6

It isn't solved. I've run out of ideas.

[solved] Virtualbox quite suddenly can't access shared folder anymore

Hi, a Windows 7 guest quite suddenly can't access a shared folder anymore. If I open the shared folder, I get a BlueScreen and Windows 7 immediately crashes and restarts, see aur-general. In the meantime I tested 3 different kernels and restored Windows 7 from a snapshot, as well as Windows 7 and ~/.VirtualBox/ from a backup. Windows doesn't provide useful information, but the VirtualBox logs mention "Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE", which seems to lead to a vboxdrv.rules issue. However, even after getting rid of the "Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE" message, by using vboxdrv.rules from the community package, the Windows guest still crashes, see aur-general.

No sound or internet with Virtualbox 6 (at least with ALSA and NAT AFAIK)

https://www.virtualbox.org/ticket/18692

@dbermond Muchas Gracias! Already building it :-)

@peschu package updated.

will there be an update to 6.0.6? my extensions already upgraded to 6.0.6 :-/

Latest Virtualbox doesn't play ALSA audio with Windows 8.1 Guest. This seems like a regression, downgrading to 5.0.40 seems to be the only solution.

Note: 6.0.0 VirtualBox (the console) would coredump when accessed via ssh -X and Win7 guests run --headless and accessed via rdesktop were unusable. Oracle released 5.2.24 today and building and downgrading resolved all problems. (5.2 branch will be supported through 2020) Also released today was 6.0.2 (I have not tried it yet). This problem was worked on the vbox-users mailing list, but no bug filed as of yet.

Your decision makes sense, but it breaks my workflow. Fortunately I even don't need to use NoExtract of pacman.conf, since /usr/local/bin is head of PATH.

$ ls -hAl /usr/bin/virtualbox*
lrwxrwxrwx 1 root root 31 Dec 31 15:46 /usr/bin/virtualbox -> ../../opt/VirtualBox/VirtualBox
lrwxrwxrwx 1 root root 33 Dec 31 15:46 /usr/bin/virtualboxvm -> ../../opt/VirtualBox/VirtualBoxVM
$ echo $PATH | cut -d: -f1
/usr/local/bin
$ ls -hAl /usr/local/bin/virtualbox 
lrwxrwxrwx 1 root root 28 Dec 30 05:15 /usr/local/bin/virtualbox -> /opt/VirtualBox/VirtualBoxVM

Guten Rutsch!

Ralf

@Ralf_Mardorf I accidentally removed a line that broke this. Now fixed.

Hi,

neither a soft link, nor the PATH variable provide to run the new command, providing the old options such as "--startvm", without using the complete path to the command.

It was like this

$ pacman -Q virtualbox-bin
virtualbox-bin 5.2.22-1
$ pacman -Ql | grep /bin/virtualbox
virtualbox-bin /usr/bin/virtualbox
$ ls -hl /usr/bin/virtualbox
lrwxrwxrwx 1 root root 26 Nov 11 18:25 /usr/bin/virtualbox -> /opt/VirtualBox/VirtualBox
$ /usr/bin/virtualbox --help | grep -e --startvm
  --startvm <vmname|UUID>    start a VM by specifying its UUID or name

and changed to

$ pacman -Q virtualbox-bin
virtualbox-bin 6.0.0-1
$ ls -hl /usr/bin/virtualbox
ls: cannot access '/usr/bin/virtualbox': No such file or directory
$ /usr/bin/VirtualBox --help | grep startvm
If you are looking for --startvm and related options, you need to use VirtualBoxVM.
$ pacman -Ql virtualbox-bin | grep VirtualBoxVM -m1
virtualbox-bin /opt/VirtualBox/VirtualBoxVM
$ grep Exec /opt/VirtualBox/virtualbox.desktop -m1
Exec=VirtualBox %U
$ grep Exec /usr/share/applications/virtualbox.desktop -m1
Exec=VirtualBox %U

Since the desktop files were always using VirtualBox and people writing scripts usually avoid CamelCase, it makes sense to add a new link /usr/bin/virtualbox against /opt/VirtualBox/VirtualBoxVM. Too funny, my several years old script already separated VirtualBox from virtualbox. Don't ask me why I added the %U to the script, looks like a copy and paste error from a desktop file :D.

$ ls -hAl /usr/local/bin/vbox
-rwxr-xr-x 1 root root 157 Jul 17  2014 /usr/local/bin/vbox
$ grep case -A3 /usr/local/bin/vbox 
case $* in
 "") VirtualBox %U ;;
  *) virtualbox --startvm "$*" ;;
esac

However, even if you don't want to add a /usr/bin/virtualbox link, at least add a link /usr/bin/VirtualBoxVM against /opt/VirtualBox/VirtualBoxVM, as it is done for VirtualBox:

$ pacman -Ql virtualbox-bin | grep /usr/bin/VirtualBox
virtualbox-bin /usr/bin/VirtualBox
$ ls -hAl /usr/bin/VirtualBox
lrwxrwxrwx 1 root root 31 Dec 30 01:34 /usr/bin/VirtualBox -> ../../opt/VirtualBox/VirtualBox

Guten Rutsch!

Ralf

While I agree that if an AUR helper should fail, the user has to try to build it without a helper, before adding a comment, we shouldn't spread myths regarding yaourt. A lot of users are satisfied by yaourt, there are not many use cases when yaourt could fail. Actually, I build 5.2.22-1 using yaourt 1.9-1 without any issue at all. IIUC the OP was able to build and install virtualbox. If the OP wants to learn what was going wrong regarding the permissions, I recommend to repeat everything and post the used commands and their complete output to an Arch forum, assuming googling shouldn't already enlighten the OP.

I'd recommend not to use yaourt in the first place. It's proven to be unsafe, is deprecated and no longer actively maintained.

If u really must use an AUR helper, I'd suggest taking a look at the Arch Wiki page before choosing one.

Even better would probably be to simply use Arch's default tooling, i.e. makepkg, or but maybe that's more of a personal preference.

I have installed virtualbox-bin 5.22 but at the end of install. I have this error /usr/lib/yaourt/aur.sh: line 211: cd: /root: Permission denied

Can anyone help me ?

Thanks,

Yep, SDK is now included in the package.

Yikes, whatever changes were made to accommodate the SDK or in the 5.2.20 release has ballooned the package size by 31.74 MiB. Is that expected? I haven't seen that big of a jump in vbox package size in years.

@Kr1ss Thank you for reporting this. Fixed.

There seems to be a conflict w/ the virtualbox-sdk package from community @dbermond (b/c of usr/lib/python3.7/site-packages/vboxapi*).

Would u pls consider adding that to the PKGBUILD ?

Thx a lot for the package, btw !

EDIT : Thank you for fixing this so quickly !

@GeneArch Please do not report problems when using a modified PKGBUILD.

I don't know if this will be a problem in future upstream stable releases.

with the older 5.2.16 everything works fine.

So its the development snapshots this is happening with. Do you know if this will be a problem when those migrate to released builds?

thanks

Sorry, this happens with the development snapshots:

https://www.virtualbox.org/wiki/Testbuilds

pkgver=5.2.97 _build=123594

which i built by obvious tweaks to your PKGBUILD.

I need to go back and test 5.2.16.

@GeneArch I cannot reproduce your issue. VirtualBox is loading fine for me and everything is working as expected. Tested with Plasma and LXQt.

You said Plasma 5.11.1 but I think that you mean Qt 5.11.1, because Plasma is currently at 5.13.3.

Here is a link to a possibly related problem: https://www.virtualbox.org/pipermail/vbox-dev/2018-July/015046.html.

Please share your solution if you find something.

Running on plasma 5.11.1 i get problems with this package running setuid. Error on attempting to run Virtualbox gives:

Qt FATAL: FATAL: The application binary appears to be running setuid, this is a security hole. Aborted

Removing the setuid - app now starts but then complains it needs to be setuid root.

Thoughts on how to fix?

Thanks

gene

Only change from 5.2.12 to 5.2.14 are:

  pkgver=5.2.14
 _build=123301

 sha256sums=('2ea513dadaab9b32df6c18827ebfe98524e297d2b44678ce1518a3486d8b3e73'
             '0aebe22abab402ea6b6573af637a99d8056a904920a52d84fb97729219219c23'
             '69417a9e8855cab8e4878886abe138f559fd17ae487d4cd19c8a24974a8bbec2'
             '656905de981ffa24f6f921c920538854a235225053f44baedacc07b46ca0cf56'
             '12dbba3b59991f2b68cddeeeda20236aeff63e11b7e2d1b08d9d6a82225f6651'
             'cc1c0500ab07bc13563d99037f776bf64bdc90bb521e31e2e0b04e42ea5bb36a'
             'e9df0fff15184d0a90abe17707bdbe1931582433bbc14ded4fb3b0252653c801'
             '5112f0e1ba3bd0bd92ef2edb2d21024e265abb02841aa29aa05410526adc273f')

I don't have much use for this. If anyone needs help adopting this, let me know

The only changes to PKGBUILD between 5.2.2 and 5.2.4 are:

pkgver=5.2.4
_build=119785

md5sums=('70973209cc9bc0e82e40a34362061f96'
     '2d04c2e2d8c71558c910a51ec773731a'
     'fe60f9510502bea67383d9198ae8c13c'
     'c159d683ba1947290fc2ad2c64194150'
     '3ac185709bfe688bb753c46e170d0546'
     '31144fa409c0d7c6b464d44b2140b521'
     '05175249e1206c491b2b36670e8db9ec'
     'c32a61f3a1611e184098cc9b0d6765bb')

All diff/patch hunks succeed, but several will be off by 1 - 8 bytes of context. So for future updates, I suspect new diffs will need to be taken. For now, the changes above have 5.2.4 happily installed and running with the extension-pack just as they always have.

If it helps, the update PKGBUILD update required for 5.2.2 is simply:

pkgver=5.2.2 _build=119230

Works fine -- even loads the modules after install (unlike 5.2.0 -- but still messes with the setvideomodehint for current vms) Smoother than 5.2.0. It's a keeper. (not to mention the forced move to 5.2.X due to the 4.14 kernel update)

Linux 4.14.3-1 is provided by "Core". Trying to build the modules still results in the same errors. "Linux hosts: fixed kernel module compilation and start failures with Linux kernel 4.14 (bug #17267)" - https://www.virtualbox.org/wiki/Changelog

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.

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

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

$ 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

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]

# 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

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)

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

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.

Gary, On behalf of the entire AUR community, 'THANK YOU' for adopting this package. Kindest Regards, Dietrich T. Schmitz

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

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.

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.

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.

"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.

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!

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.

The conflicts are wrong. The host modules have been renamed? virtualbox-host-dkms virtualbox-host-modules-arch

Thank you for the patch k0ste.

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=

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"

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

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

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.

pkgver=5.0.6 _build=103037 md5 9d67e2df72630dc2ac5983c7cdb1cf5f Worked like a charm again.

Thanks for making this package. I tested with the updates below and had no issues. pkgver=5.0.4 _build=102546 md5 8028829331bc0822fa2d2d3cf301dda3