Arch Linux User Repository

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.

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.

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

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

@dbermond Muchas Gracias! Already building it :-)

@peschu package updated.

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

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.

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.

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

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

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