Package Details: virtualbox-bin 6.0.8-1

Git Clone URL: https://aur.archlinux.org/virtualbox-bin.git (read-only)
Package Base: virtualbox-bin
Description: Oracle VM VirtualBox Binary Edition (Oracle branded non-OSE version)
Upstream URL: https://www.virtualbox.org/
Keywords: machine oracle virtualization vm
Licenses: GPL2
Conflicts: virtualbox, virtualbox-host-dkms, virtualbox-host-modules-arch, virtualbox-sdk
Provides: VIRTUALBOX-HOST-MODULES, virtualbox=6.0.8, virtualbox-guest-iso, virtualbox-host-dkms, virtualbox-sdk
Replaces: virtualbox-sun, virtualbox_bin
Submitter: Rainmaker
Maintainer: dbermond
Last Packager: dbermond
Votes: 50
Popularity: 0.874005
First Submitted: 2015-08-18 09:16
Last Updated: 2019-05-18 17:30

Dependencies (14)

Required by (43)

Sources (12)

Latest Comments

1 2 3 4 5 6 Next › Last »

shillshocked commented on 2019-06-06 23:01

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

@dbermond Muchas Gracias! Already building it :-)

dbermond commented on 2019-04-19 15:21

@peschu package updated.

peschu commented on 2019-04-18 22:15

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

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

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.

Ralf_Mardorf commented on 2018-12-31 15:08

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

dbermond commented on 2018-12-31 11:40

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

Ralf_Mardorf commented on 2018-12-30 03:58

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

Ralf_Mardorf commented on 2018-11-12 19:27

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.