Discuss the 5.1.20 release

[frank]

Discuss the 5.1.20 release here.
You can download the release here.

[socratis]

From the VirtualBox blog, there was this:

VirtualBox 5.1.20 and 5.0.38 include all the security fixes part of "April 2017 Oracle CPU" and you can see all the details here.

where "here" leads to the "Oracle Critical Patch Update Pre-Release Announcement - April 2017". This seems to be a huge one, as it affects almost everything Oracle-branded. As far as VirtualBox is concerned, we have:

Oracle Virtualization Executive Summary

• This Critical Patch Update contains 15 new security fixes for Oracle Virtualization. 6 of these vulnerabilities may be remotely exploitable without authentication, i.e., may be exploited over a network without requiring user credentials.
  
  The highest CVSS Base Score of vulnerabilities affecting Oracle Virtualization is 9.8
  
  The Oracle Virtualization components affected by vulnerabilities that are fixed in this Critical Patch Update are:
  • Oracle VM VirtualBox
  • Secure Global Desktop

Any comment on what the problems might have been? I'm asking because I didn't see anything mentioned in the announcement or in the Changelog.

[socratis]

Major issue on OSX 10.9.5
Host: OSX 10.9.5
Guest: None of the VMs that have 3D acceleration enabled will start.

Failed to open a session for the virtual machine Windows 7.
This VM was configured to use 3D acceleration. However, the 3D support of the host is not working properly and the VM cannot be started. To fix this problem, either fix the host 3D support (update the host graphics driver?) or disable 3D acceleration in the VM settings (VERR_NOT_AVAILABLE).

• Result Code: NS_ERROR_FAILURE
               (0x80004005)
  Component:   ConsoleWrap
  Interface:   IConsole
               {872da645-4a9b-1727-bee2-5585105b9eed}

And if you go to the VM settings, you get the "Invalid settings" warning sign with the following message:

Display: Screen page:
The virtual machine is set up to use hardware graphics acceleration. However the host system does not currently provide this, so you will not be able to start the machine.

Edit: Created ticket #16665: 3D support must be disabled, otherwise VMs won't start Fixed with build >= 114629.

[socratis]

Host: OSX 10.9.5
On the same subject (graphics), why is 2D acceleration setting disabled altogether? You can't enable or disable it, it's stuck to the previous value (from 5.1.18 I mean). Or if you know your way, you can edit the .vbox file...

Something went really wrong here...

Edit: Created ticket #16666: 2D acceleration setting disabled on OSX (10.9.5) Fixed with build >= 114629.

[socratis]

Host: Win7-64
Installed 5.1.20. Launched 5.1.20 right after the installation. Immediately greeted with the "You have an older version of VirtualBox installed (5.1.16)." Most probably the version check happens before checking the actual file running?

I forgot to back up my VirtualBox.xml file before that, so I can't easily re-create it. But I could try fiddling with the settings...

[mjanicki]

I can't figure out how to fix it, so perhaps someone has an idea.

5.1.20 fails to build on a Slackware box due to what seems to be unavailable source files. Specifically, the files:

VirtualBox-5.1.20/src/VBox/HostDrivers/Support/posix/SUPR3HardenedMain-posix.cpp
VirtualBox-5.1.20/src/VBox/HostDrivers/Support/posix/SUPR3HardenedMainA-posix.asm

cause build failure with the following type of error message:

kmk: *** No rule to make target `/var/tmp/SBo/VirtualBox-5.1.20/src/VBox/HostDrivers/Support/posix/SUPR3HardenedMain-posix.cpp', needed by `/var/tmp/SBo/VirtualBox-5.1.20/out/linux.amd64/release/obj/SUPR3HardenedStatic/posix/SUPR3HardenedMain-posix.o'. Stop.

Thanks for any input as to what I am likely doing wrong.

[frank]

I can't figure out how to fix it, so perhaps someone has an idea.

5.1.20 fails to build on a Slackware box due to what seems to be unavailable source files. Specifically, the files:

VirtualBox-5.1.20/src/VBox/HostDrivers/Support/posix/SUPR3HardenedMain-posix.cpp
VirtualBox-5.1.20/src/VBox/HostDrivers/Support/posix/SUPR3HardenedMainA-posix.asm

cause build failure with the following type of error message:

kmk: *** No rule to make target `/var/tmp/SBo/VirtualBox-5.1.20/src/VBox/HostDrivers/Support/posix/SUPR3HardenedMain-posix.cpp', needed by `/var/tmp/SBo/VirtualBox-5.1.20/out/linux.amd64/release/obj/SUPR3HardenedStatic/posix/SUPR3HardenedMain-posix.o'. Stop.

Thanks for any input as to what I am likely doing wrong.

Thanks for the report. These 2 files were missing in the original tarball. We've created a new tarball (VirtualBox-5.1.20a.tar.bz2). All links are adapted. See also ticket 16669.

[erdeslawe]

Host: MacOS 10.12.4

Windows 10 Guests will not start unless 3D Acceleration is disabled.

[chris-2point0]

Hi all,

I've just updated to 5.1.20 and noticed that my linux guests were unable to mount the shared folders:

Host: Linux / Ubuntu 16.04.2
Guest: Linux / Ubuntu 16.04.2

Issue
Guest is unable to mount shared folders.

Error Msg
chris@guest:/> sudo mount /media/sf_downloads/
mount: mount downloads on /media/sf_downloads failed: Protocol error

dmesg
(not sure if this is related)
...
sf_read_super_aux err=-71
...

Root cause
/sbin/mount.vboxsf is (sym-)linked to a non-existent file:

Code: Select all

chris@guest:/> ll /sbin/mount.vb*
lrwxrwxrwx 1 root root     49 Apr 19 12:49 mount.vboxsf -> /opt/VBoxGuestAdditions-5.1.20/other/mount.vboxsf

Fix
find correct location & replace existing symlink

Code: Select all

chris@guest:/> find /opt/VBoxGuestAdditions-5.1.20/ -name mount.vboxsf
/opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.vboxsf

Code: Select all

chris@guest:/> sudo rm/sbin/mount.vboxsf
chris@guest:/> sudo ln -s /opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.vboxsf  /sbin/mount.vboxsf

That did the trick for me.

regards,

chris

[socratis]

Host: MacOS 10.12.4
Windows 10 Guests will not start unless 3D Acceleration is disabled.

Thanks for confirming it's not just OSX 10.9.5 that has the problem. Can you also test any other guest? Even FreeDOS would do, or any other Linux LiveCD, as long as 3D is enabled in the settings. See: #16665: 3D support must be disabled, otherwise VMs won't start.

Also, since I got your attention, can you also check for #16666: 2D acceleration setting disabled on OSX (10.9.5)? I'd like to know if it's an OSX 10.9.5 host problem or an OSX host problem in general. I do not see it in a Win7 or a Win10 host.

Edit: Both issues fixed with build >= 114629.

[frank]

Host: MacOS 10.12.4
Windows 10 Guests will not start unless 3D Acceleration is disabled.

Thanks for confirming it's not just OSX 10.9.5 that has the problem. Can you also test any other guest? Even FreeDOS would do, or any other Linux LiveCD, as long as 3D is enabled in the settings. See: #16665: 3D support must be disabled, otherwise VMs won't start.

Also, since I got your attention, can you also check for #16666: 2D acceleration setting disabled on OSX (10.9.5)? I'd like to know if it's an OSX 10.9.5 host problem or an OSX host problem in general. I do not see it in a Win7 or a Win10 host.

Thanks socratis for the quick reports and for creating the tickets and thanks to all other reporters. I think we fixed this regression. Both 5.1.20 and 5.0.38 are affected on Mac OS X. I've replaced the 5.1.20 build for Mac OS X. The fixed revision number is 114629 (the buggy one was 114628). I will also update the tickets. Please confirm that using the 5.1.20 114629 build you are again able to enable 2D/3D for your VMs. Thanks!

[socratis]

Please confirm that using the 5.1.20 114629 build you are again able to enable 2D/3D for your VMs.

Excellent! Two birds with one stone!!! That was really quick!
Now if we could apply the same "fast" algorithm for the remaining 2650 open tickets, we'd have a bug free program in less than a week!

Thanks! Will update the posts and the tickets.

[mjanicki]

Just to confirm something that was recently reported in bug ticket #16667; I'm seeing the same thing with ALSA Audio on guests using a Linux host.

Host: Linux (Slackware)
Guests: OpenSolaris, Haiku, FreeBSD
VBox: 5.1.20 (5.1.18 worked)

With VBox 5.1.20, guest audio (for all 3 guests) fails during guest startup. Error message indicates that "null audio" is being selected as no audio device could be found. With 5.1.18 host audio works as expected.

Audio settings for each guest is:
Host Driver: ALSA Audio Driver
Controller: ICH AC97

Each guest has an associated AC97 device showing in respecitve device listings. I've tried resetting the sound configuration for each guest with no change. I also created a new VM and that VM showed the same audio issue. I tried switching VBox Audio Controller to Intel HD Audio to no avail.

What I thik to be necessary/helpful log output below (.ascoundrc does define a device named "default"):

Code: Select all

00:00:00.645923 [/Devices/ichac97/] (level 2)
00:00:00.645924
00:00:00.645925 [/Devices/ichac97/0/] (level 3)
00:00:00.645927   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:00.645928   PCIDeviceNo   <integer> = 0x0000000000000005 (5)
00:00:00.645929   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:00.645930   Trusted       <integer> = 0x0000000000000001 (1)
00:00:00.645931 
00:00:00.645932 [/Devices/ichac97/0/AudioConfig/] (level 4)
00:00:00.645934
00:00:00.645934 [/Devices/ichac97/0/Config/] (level 4)
00:00:00.645936   Codec <string>  = "STAC9700" (cb=9)
00:00:00.645937
00:00:00.645938 [/Devices/ichac97/0/LUN#0/] (level 4)
00:00:00.645940   Driver <string>  = "AUDIO" (cb=6)
00:00:00.645941
00:00:00.645941 [/Devices/ichac97/0/LUN#0/AttachedDriver/] (level 5)
00:00:00.645944   Driver <string>  = "ALSAAudio" (cb=10)
00:00:00.645945
00:00:00.645945 [/Devices/ichac97/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:00.645947   StreamName <string>  = "Haiku" (cb=6)
00:00:00.645948
00:00:00.645949 [/Devices/ichac97/0/LUN#0/Config/] (level 5)
00:00:00.645951
00:00:00.645952 [/Devices/ichac97/0/LUN#1/] (level 4)
00:00:00.645953   Driver <string>  = "AUDIO" (cb=6)
00:00:00.645954
00:00:00.645955 [/Devices/ichac97/0/LUN#1/AttachedDriver/] (level 5)
00:00:00.645957   Driver <string>  = "AudioVRDE" (cb=10)
00:00:00.645958
00:00:00.645958 [/Devices/ichac97/0/LUN#1/AttachedDriver/Config/] (level 6)
00:00:00.645960   AudioDriver      <string>  = "AudioVRDE" (cb=10)
00:00:00.645962   Object           <integer> = 0x00007fa22400ffe0 (140 334 365 474 784)
00:00:00.645964   ObjectVRDPServer <integer> = 0x00007fa2240100c0 (140 334 365 475 008)
00:00:00.645966   StreamName       <string>  = "Haiku" (cb=6)

=======================================

00:00:00.695446 Audio: Initializing ALSA driver
00:00:00.695458 Audio: Using VBox 5.0.x audio code!
00:00:00.700998 Audio: Host audio backend supports 1 output streams and 1 input streams at once
00:00:00.701055 Audio: Initializing VRDE driver
00:00:00.701065 Audio: Using VBox 5.0.x audio code!
00:00:00.701075 Audio: Host audio backend supports 1 output streams and 2 input streams at once
00:00:00.701088 AC97: Reset
00:00:00.701894 ALSA: Failed to open "default" as input device: No such file or directory
00:00:00.702648 ALSA: Failed to open "default" as input device: No such file or directory
00:00:00.703375 ALSA: Failed to open "default" as output device: No such file or directory
00:00:00.704037 ALSA: Failed to open "default" as output device: No such file or directory
00:00:00.704108 AC97: Falling back to NULL backend (no sound audible)
00:00:00.704114 AC97: Reset
00:00:00.704151 Audio: Initializing NULL driver
00:00:00.704156 Audio: Using VBox 5.0.x audio code!
00:00:00.704160 Audio: Host audio backend supports 1 output streams and 2 input streams at once

Thanks.

[Petr Vones]

From the VirtualBox blog, there was this:
Any comment on what the problems might have been? I'm asking because I didn't see anything mentioned in the announcement or in the Changelog.

Second that. I am usually slow with updates but this one would mean to apply the update immediately. Thanks.

[pjw9]

I as well lost audio after upgrading to 5.20. Debian Stretch, Alsa Audio, Windows 7 guest.

Just to confirm something that was recently reported in bug ticket #16667; I'm seeing the same thing with ALSA Audio on guests using a Linux host.