Package Details: virtualbox-bin-sdk 7.0.14-1

Git Clone URL: https://aur.archlinux.org/virtualbox-bin.git (read-only, click to copy)
Package Base: virtualbox-bin
Description: VirtualBox software developer kit for use with virtualbox-bin package
Upstream URL: https://www.virtualbox.org/
Keywords: machine oracle virtualization vm
Licenses: GPL2, custom, BSD, LGPL2.1
Conflicts: virtualbox-sdk
Provides: virtualbox-sdk
Submitter: Rainmaker
Maintainer: dbermond
Last Packager: dbermond
Votes: 62
Popularity: 0.027486
First Submitted: 2015-08-18 09:16 (UTC)
Last Updated: 2024-01-18 15:25 (UTC)

Dependencies (3)

Required by (7)

Sources (12)

Pinned Comments

dbermond commented on 2022-10-21 19:08 (UTC)

Notice:

To avoid crashes when upgrading Guest Additions from version 6.x to 7.x on Windows guests, uninstall the old Guest Additions first, then reboot, and then install the new ones. It's recommended to do all these operations in Safe Mode. See this upstream bug ticket for more details.

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 Next › Last »

drankinatty commented on 2017-11-10 05:58 (UTC) (edited on 2017-11-10 05:59 (UTC) by drankinatty)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC) (edited on 2017-04-25 15:25 (UTC) by shillshocked)

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 (UTC)

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.

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 Next › Last »