Package Details: virtualbox-bin 7.1.10-1

Git Clone URL: https://aur.archlinux.org/virtualbox-bin.git (read-only, click to copy)
Package Base: virtualbox-bin
Description: Powerful x86 virtualization for enterprise as well as home use (Oracle branded non-OSE)
Upstream URL: https://www.virtualbox.org/
Keywords: machine oracle virtualization vm
Licenses: GPL-3.0-only
Conflicts: virtualbox, virtualbox-host-dkms, virtualbox-host-modules-arch
Provides: virtualbox, virtualbox-host-dkms, VIRTUALBOX-HOST-MODULES
Replaces: virtualbox-sun, virtualbox_bin
Submitter: Rainmaker
Maintainer: dbermond
Last Packager: dbermond
Votes: 63
Popularity: 0.144338
First Submitted: 2015-08-18 09:16 (UTC)
Last Updated: 2025-06-04 14:56 (UTC)

Required by (14)

Sources (13)

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 .. 5 6 7 8 9 10 11 12 13 14 15 Next › Last »

Romario74 commented on 2020-03-31 14:41 (UTC)

dkms modules do not build with kernel 5.6

Ralf_Mardorf commented on 2019-07-28 16:29 (UTC)

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

Ralf_Mardorf commented on 2019-07-28 14:14 (UTC) (edited on 2019-07-28 14:14 (UTC) by Ralf_Mardorf)

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

Ralf_Mardorf commented on 2019-07-27 17:50 (UTC) (edited on 2019-07-27 17:51 (UTC) by Ralf_Mardorf)

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.

shillshocked commented on 2019-06-06 23:01 (UTC)

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

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

peschu commented on 2019-04-19 17:02 (UTC)

@dbermond Muchas Gracias! Already building it :-)

dbermond commented on 2019-04-19 15:21 (UTC)

@peschu package updated.

peschu commented on 2019-04-18 22:15 (UTC)

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

shillshocked commented on 2019-04-08 07:17 (UTC)

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.

drankinatty commented on 2019-01-16 01:42 (UTC) (edited on 2019-01-16 01:43 (UTC) by drankinatty)

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.

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