Arch Linux User Repository

There is no version dependency on this package on purpose! You could read comments back from 2011 to understand why.

@jamesan, you are hired, you are the top candidate to inherit this package... I saw that new license on VBoxManage install on SuSE, but didn't take time to translate that into the post-install here. Great job!

@jamesan ... neat, thanks for sharing!

tl;dr: package installs/upgrades complete with errors and the extension pack is not successfully added to VirtualBox. Either manually install the extension pack using the CLI VBoxManage command or the VirtualBox GUI after the erroneous install/upgrade or replace the package's post_install() function with prior to install/upgrade: post_install () { VBoxManage extpack install --accept-license=$(sha256sum /usr/share/licenses/virtualbox-ext-oracle/PUEL | head --bytes=64) "/usr/share/virtualbox/extensions/Oracle_VM_VirtualBox_Extension_Pack-${1%%-*}.vbox-extpack" >/dev/null } ---- The `VBoxManage extpack install` command fails when run within a script (non-interactively). When run interactively, it requires user acceptance of its license and outputs how to run it non-interactively -- namely, by adding the argument, --accept-license=$HASH, where $HASH is derived to equal the SHA256 hash value of the text file version of the extension pack license (the extracted ./ExtPack-license.txt in the extpack archive file, also installed by this package to /usr/share/licenses/virtualbox-ext-oracle/PUEL). I can confirm this derivation holds true for at least version 5.1.20. Without changes, upgrading or installation fails at the post_install() VBoxManage command with pacman outputting an "error: command failed to execute correctly" message and the extension pack is not added to VirtualBox. With the above change, the package installs without exception and VirtualBox recognises the new extension pack.

As was generally the case, it was the end-user doing something stupid. I had an old version of the guest-additions installed that conflicted with the auto-build of the new modules. 5.1.18 works just fine. Sorry for the noise.

@drankinatty, is your host and your guest arch linux? you need virtualbox-ext-oracle for your host only.

You say "Build fails for both 5.1.18 and 5.1.16."?

Note: when bumping the version to 5.1.18, building/installing the extension pack package worked fine, but when attempting to build the kernel modules for an Arch guest with the 4.10 kernel, I ran into a build failure. Reported upstream: https://www.virtualbox.org/ticket/16576.

@yan12125, I had the same problem but upgrading to the latest version of virtualbox-ext-oracle solved the problem.

Hello seblu, I know there's already an out-of-date flag, while things are somewhat different this time. With virtualbox 5.1.10, virtual machines refuse to start with older extension packs: $ vboxmanage startvm win7 Waiting for VM "win7" to power on... VBoxManage: error: The device helper structure version has changed. VBoxManage: error: If you have upgraded VirtualBox recently, please make sure you have terminated all VMs and upgraded any extension packs. If this error persists, try re-installing VirtualBox. (VERR_PDM_DEVHLPR3_VERSION_MISMATCH) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole virtualbox has just entered [community] 90 minutes ago, so I just more people will be affected by this issue. For others come here, perlsite's comment below (on 2016-07-01 18:32) is helpful. Just change pkgver=5.1.10 and md5sum to ac90d8356746754eadc3f28ef77174f0