Discuss the 5.1.4 release

[Papolytic]

Where are (if there are any) the change logs for the ../testBuilds versions?

Thanks.

[The Raven]

A test build is now available, this is just the Extension Pack

Michaln,
Just to confirm ... Do I only need to install the Extension Pack, Version 110310
on top of my existing VB 5.1.4 install ?

Apologies for double-checking but I'm fairly new to VirtualBox and wish to ensure
I've got a valid installation for my regression tests.

Thank you.

[michaln]

Just to confirm ... Do I only need to install the Extension Pack, Version 110310
on top of my existing VB 5.1.4 install ?

Yes. That's where the change/fix is.

[oldium]

In 5.1.4 the VirtualBox interface process (VBoxSvc.exe) does not want to terminate. I do not know if it is related to my new use case or simply problem of 5.1.4 - I started to attach USB devices to my hosts (Intel Edison Board, Windows Phone) and now the VirtualBox Interface process (VBoxSvc.exe) does not want to terminate when I want to shut-down the system. Host Win 10 (latest anniversary update), guests Win 10 and Ubuntu 14.04.4 LTS. Win 10 guest log attached.

[ssawgift]

In 5.1.4 the VirtualBox interface process (VBoxSvc.exe) does not want to terminate. I do not know if it is related to my new use case or simply problem of 5.1.4 - I started to attach USB devices to my hosts (Intel Edison Board, Windows Phone) and now the VirtualBox Interface process (VBoxSvc.exe) does not want to terminate when I want to shut-down the system. Host Win 10 (latest anniversary update), guests Win 10 and Ubuntu 14.04.4 LTS. Win 10 guest log attached.

The problem started a few releases ago. I almost have this bug everyday when I shutdown my computer.

[The Raven]

Michaln,
As it was only the Extension Pack to upgrade and my end-of-day
backups would provide an initial test, I was able to use my machine
with real USB 3.0 ports.

Regression test results for VirtualBox Extension Pack 5.1.51-110310
The main VB install was kept at 5.1.4-110228 as were the GA within the guest.

Host : Debian 8.5 running "stable" but with Kernel 4.6.4 from backports

Windows Guest :
Windows 7 Professional SP1 + all patches up to and inc. August Patch Tuesday
USB 3 drivers : Intel xHCI drivers 1.0.10.255

First tests run with USB controller still set at 2.0
USB 2.0 capable drive attached to USB 3.0 host port - OK
USB 2.0 capable drive attached to USB 2.0 host port - OK
Low-speed printer and flatbed scanner attached to host USB 2.0 ports - OK

Second tests run with USB controller set to 3.0 (xHCI)
USB 2.0 capable drive attached to USB 3.0 host port - OK
USB 2.0 capable drive attached to USB 2.0 host port - OK
USB 3.0 capable drive attached to USB 3.0 host port - OK
USB 3.0 capable drive attached to USB 2.0 host port - OK
(correctly received warning in Windows saying device can run faster)
Low-speed printer and flatbed scanner attached to host USB 2.0 ports - OK

Attachment method used was both by filter and via the Device drop-down.

I then re-ran all the above tests - with the exception of those requiring
USB 3.0 ports - on my Test/Hot-Spare system. All tests passed, as above.
The installed software on my test system is the same as my main "live"
machine, so these tests were really to ensure it all worked on (slightly)
different hardware.

Further tests :
As I originally encountered the Linux boot hang described by problem ticket
15747 for which 5.1.4 contained a workaround, I also ensured that my two
Linux Guests (Mint Debian 32-bit and Mint Debian 64-bit) still booted
correctly with the Extension Pack under test, which they did.

Hopefully I have covered most of the obvious tests but if there are any
others that you think may be worthwhile, please ask.

Thank you.

[michaln]

Thanks for the very comprehensive test report, Raven! That should be quite sufficient.

[Organic_Marble]

Any movement on fixing the snapshot deletion problem? I never realized how much I relied on this functionality. In the words of Joni Mitchell, "You don't know what you've got, till it's gone"! I even tried rolling back to a earlier Virtualbox release to get the functionality back, but that was very painful.

[Vmboxuser]

The same problem as with 5.1.2

Failed to acquire the VirtualBox COM object.

The application will now terminate.



Callee RC: E_NOINTERFACE (0x80004002)

On my system only version 4.1.28 works... 5.x, 4.3, 4.2 are not working

Win 7 SP1 x86

In my case the problem was because RegQueryKey of HKCU\Software\Classes\CLSID\{00020420-0000-0000-C000-000000000046} returned BUFFER TOO SMALL
So, I've deleted HKCU\Software\Classes\CLSID\{00020420-0000-0000-C000-000000000046} and now Virtualbox starts. But when I press Start button -

Failed to open a session for the virtual machine CentOS.

Result Code: E_FAIL (0x80004005)

[rowland]

I would also like to know if there has been any movement on the snapshot deletion problem. I added some more details to this ticket:

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

I don't know how useful that information is, but it seems like this should be easy to duplicate. It doesn't seem like anyone owns that ticket yet, and I am not aware of another better ticket (though I have not looked since I updated that one).

[Anunes]

Just want to give feedback.

VBOX / GuestAditions 110484
Host Win 10 - 1607.105

Issues:
-General performance degradation in Host, also in Networking in Host between other PC (not guests involved)
-Starting or closing a Win Guest, Bluetooth Devices in Host is being disconnected.

Vbox 110394 is good, no problems.

EDIT: The Bluetooth is a Combo WLan+BT 4 internal Card. Intel AC7260

[Papolytic]

I would also like to know if there has been any movement on the snapshot deletion problem. I added some more details to this ticket:

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

I don't know how useful that information is, but it seems like this should be easy to duplicate. It doesn't seem like anyone owns that ticket yet, and I am not aware of another better ticket (though I have not looked since I updated that one).

I'd like to hear about this as well. Although I'm keeping up with the 5.1.5 branch of testBuilds, I don't have 7 hours to test snapshot deletion (backup/restore) each time and I can't find anything resembling changelogs for the 5.1.5 test builds. Many thanks.

Edit:: I installed the testBuilds of today (5.1.5, *) and tried a 2 .vdi VM quick install of Ubuntu in order to quickly test deleting a snapshot in the latest builds. They fail. I also don't notice anything of use in the log file. Is there something in particular you're wanting to help debug this?

Edit #2: I'm trying 5.1.5 110598 build but without any vbox processes running in the background (to get rid of snapshots that are piling up): I'm using this command from an admin cmd shell:

Code: Select all

C:\Program Files\Oracle\VirtualBox> vboxmanage snapshot myUbuntuGuest list --machinereadable
SnapshotName="UB16.04 LTS: VB51"
SnapshotUUID="7115426f-1d4c-4ef8-9e79-45ed5d1617a4"
SnapshotName-1="Ubuntu 16.04.1 LTS : vb5.1.4 : gt : new"
SnapshotUUID-1="4dd1e13e-ae06-4876-85c8-7a29c6e4a1b7"
SnapshotDescription-1="testing"
SnapshotName-1-1="updates : 5.1.5 testb"
SnapshotUUID-1-1="e77fd306-4569-426f-9eac-5b54c1a1c421"
SnapshotName-1-1-1="updates"
SnapshotUUID-1-1-1="85c11e87-7141-41f4-ae68-7a506bf27d06"
CurrentSnapshotName="updates"
CurrentSnapshotUUID="85c11e87-7141-41f4-ae68-7a506bf27d06"
CurrentSnapshotNode="SnapshotName-1-1-1"

I'll report back after I figure out how to delete one via vboxmanage.exe in win 7. I'm backed up so don't care if it fails.

[Papolytic]

Note *important* ::

Never mind. The success was not quite what I hoped for. It worked fine as described below until I tried the 2nd snapshot, and then I had the same problem as before using the GUI, so don't do this.

---------------


If you read the "code" section of my post above, I tried using vboxmanage to delete a snapshot of a vm with 4 vdi's.

It works fine as long as you don't have an instance of vbox* running as GUI.

Here's the command (or the like) which I used. It should be useful for troubleshooting or just cleaning up your many snapshots you can't get rid of.

Code: Select all

$ vboxmanage snapshot myUbuntuGuest delete 7115426f-1d4c-4ef8-9e79-45ed5d1617a4
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

$ vboxmanage snapshot myUbuntuGuest list --machinereadable
SnapshotName="Ubuntu 16.04.1 LTS : vb5.1.4 : gt : new"
SnapshotUUID="4dd1e13e-ae06-4876-85c8-7a29c6e4a1b7"
SnapshotDescription="testing"
SnapshotName-1="updates : 5.1.5 testb"
SnapshotUUID-1="e77fd306-4569-426f-9eac-5b54c1a1c421"
SnapshotName-1-1="updates"
SnapshotUUID-1-1="85c11e87-7141-41f4-ae68-7a506bf27d06"
CurrentSnapshotName="updates"
CurrentSnapshotUUID="85c11e87-7141-41f4-ae68-7a506bf27d06"
CurrentSnapshotNode="SnapshotName-1-1"

Note: This was the latest testBuild for 5.1.5 :: Also: It should be noted that it hangs at 90% while the actual deletion takes place, so this amount of time could vary from a few seconds to > minutes but it completes.

[Anunes]

Hi,

Just want give Feedback
Vbox 110598 GuestAdd 110599
Host W10 - 1607.105

VBox now Starts quick. Since many versions before,there was some noticeable Delay to launch.
I do not see the Windows "memory write error" that I posted here before. In Vbox 110394 there was still this errors.
Sound in Win Guest is working, I think in 110394 there was issues.
Guest are closing very fast.
In Guest the USB Devices are showing up with the right names.

Well done, congratulations.

[johnlee]

running latest win test build, shows as 5.1.5 r110598 in help in vm vbox manager. However, when running latest patched ubuntu 16.04 vm and doing a vboxmanage --version shows as 5.1.4 r110228. This appears to be the version of vbox when I installed it on ubuntu so I could run vboxmanage, not that of the current running version of vbox. Documentation doesn't make this clear.

How can I get the correct current running version no of vbox from within a ubuntu vm? j