Arch Linux User Repository

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=