Discuss the 4.3.20 release

[frank]

Discuss the 4.3.20 release here. See the changelog for details.

[smithlar]

The sha256 and md5 checksums are not available for download.
The links are broken.

[JayEm]

Old Snapshots are still crashing when restoring like in Version 4.3.18 at the state of 97%. Posted that already in the old release discussion. Not all, but quite a few.
It's a hard crash; unknown software exception (0x80000003). Worked fine in 4.3.16.

See this post.
viewtopic.php?f=1&t=64104&p=301360#p301359

There must be a change from 4.3.16 to 4.3.18 in restoration of snapshots.

[ChipMcK]

The sha256 and md5 checksums are not available for download.
The links are broken.

check out 4.3.20

Updated: Quoted wrong post <<sigh>>

[JayEm]

I've compared now the log of starting VM under 4.3.16 and 4.3.20. There seems to be some relevant lines for the snapshot-restoring bug:
Log of 4.3.16:

00:00:15.739866 HGCM: restoring [VBoxSharedFolders]
00:00:15.739915 HGCM: restoring [VBoxGuestControlSvc]
00:00:15.739986 HGCM: restoring [VBoxGuestPropSvc]
00:00:15.740003 HGCM: restoring [VBoxDragAndDropSvc]
00:00:15.740006 HGCM: restoring [VBoxSharedClipboard]
00:00:15.740168 Guest Additions information report: additionsVersion = 0x00010004, osType = 0x00033000
00:00:15.740355 Audio: set_record_source ars=0 als=0 (not implemented)
00:00:15.740588 Releasing keys...
00:00:15.740802 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000bed0000 w=1152 h=864 bpp=32 cbLine=0x1200, flags=0x1
00:00:15.740809 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4608, Size=1152x864, Sending to async-handler..
00:00:15.740846 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4608, Size=1152x864
00:00:15.740856 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content..
00:00:15.741217 NAT: set redirect TCP host port 22 => guest port 22 @ 10.0.2.15
00:00:15.771362 Changing the VM state from 'LOADING' to 'SUSPENDED'.
00:00:15.771403 Changing the VM state from 'SUSPENDED' to 'RESUMING'.
00:00:15.771570 Changing the VM state from 'RESUMING' to 'RUNNING'.
00:00:15.786441 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000bed0000 w=1152 h=864 bpp=32 cbLine=0x1200, flags=0x1
00:00:15.786452 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4608, Size=1152x864, Sending to async-handler..
00:00:15.788777 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4608, Size=1152x864
00:00:15.788789 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content..
00:00:15.894116 2D video acceleration is disabled.
00:00:15.894130 HID LEDs sync is disabled.

Log of 4.3.20:

00:00:04.371599 HGCM: restoring [VBoxSharedFolders]
00:00:04.371680 HGCM: restoring [VBoxGuestControlSvc]
00:00:04.371714 HGCM: restoring [VBoxGuestPropSvc]
00:00:04.371770 HGCM: restoring [VBoxDragAndDropSvc]
00:00:04.371776 HGCM: restoring [VBoxSharedClipboard]
00:00:04.371952 Guest Additions information report: additionsVersion = 0x00010004, osType = 0x00033000 (32-bit)
00:00:04.372266 Audio: set_record_source ars=0 als=0 (not implemented)
00:00:04.372369
00:00:04.372369 !!Assertion Failed!!
00:00:04.372369 Expression: !VMCPU_FF_IS_SET(pVCpu, VMCPU_FF_INTERRUPT_PIC)
00:00:04.372370 Location : F:\tinderbox\win-4.3\src\VBox\VMM\VMMR3\PDM.cpp(937) int __cdecl pdmR3LoadExec(struct VM *,struct SSMHANDLE *,unsigned int,unsigned int)

I have made the relevant lines bold. It seems 4.3.16 releases the keys, this was changed in 4.3.18 and 4.3.20. These versions don't release the keys anymore.

It seems to have something to do with this bug:
https://www.virtualbox.org/ticket/11289

My related posts:
viewtopic.php?f=1&t=64762#p304940
viewtopic.php?f=1&t=64104&p=301360#p301359

Any help?
I hope you can fix this problem, everything else is working fine here.

[frank]

The sha256 and md5 checksums are not available for download.
The links are broken.

Thanks! Fixed.

[zr1cbc]

On a Windows XP x64 SP2 host, starting any VM with the 4.3.20 release produces the following error message:

Failed to open a session for the virtual machine Ubuntu 12.04 LTS.

Unable to load R3 module C:\Program Files\Oracle\VirtualBox/VBoxDD.DLL (VBoxDD): GetLastError=127 (VERR_SYMBOL_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

This did not happen for release 4.3.16, which was in use prior to the update to 4.3.20.

[frank]

On a Windows XP x64 SP2 host, starting any VM with the 4.3.20 release produces the following error message:

Failed to open a session for the virtual machine Ubuntu 12.04 LTS.

Unable to load R3 module C:\Program Files\Oracle\VirtualBox/VBoxDD.DLL (VBoxDD): GetLastError=127 (VERR_SYMBOL_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

This did not happen for release 4.3.16, which was in use prior to the update to 4.3.20.

Thanks! That was a last-minute regression. Fixed by a new 4.3.20 Windows build. Just download it again. The new version is 4.3.20 r96997, the old one was 4.3.20 r96996.

[zr1cbc]

Thanks! That was a last-minute regression. Fixed by a new 4.3.20 Windows build. Just download it again. The new version is 4.3.20 r96997, the old one was 4.3.20 r96996.

The error is indeed gone with version 4.3.20 r96997. Thanks for your quick response and for the great software!

[g2flyer]

Old Snapshots are still crashing when restoring like in Version 4.3.18 at the state of 97%. Posted that already in the old release discussion. Not all, but quite a few.
It's a hard crash; unknown software exception (0x80000003). Worked fine in 4.3.16.

See this post.
viewtopic.php?f=1&t=64104&p=301360#p301359

There must be a change from 4.3.16 to 4.3.18 in restoration of snapshots.

I also still see the same problem on 4.3.20 as on 4.3.18 on Ubuntu 14.04 32-bit (see post
viewtopic.php?f=1&t=64104&start=15#p301609).
I.e., downgraded again to 4.3.14

Note: the problem might be related to extension pack? E.g., after downgrading to 4.3.14 debs but with 4.3.20 extension pack still installed, it tried to resume as usual and got the "usual" error. Once i reset the extension pack to 4.3.14, resume of the same image which previously failed now resumed properly ...

[Papolytic]

Host system: Win 7 ult. 64 bit.
Guests: 1) Ubuntu 12.04 LTS 64 bit : 2) Ubuntu 14.04 LTS 64 bit.

Installed and runs without problems that I can see. No extensive testing done yet, but 3d looks fine, and building cm11 works OK.

[swordfish]

I run LMDE (Linux Mint Debian Edition) as a 32 bit guest on a 32 bit Windows 7 host. I am running VBox 4.3.12. This morning I tried to upgrade to 4.3.20, but 4.3.20 was unable to run my guest. It would go through the loading process and at the end it would die with V_ERR_MAP. I have now retreated to the safety of 4.3.12, which still works.

[frank]

I run LMDE (Linux Mint Debian Edition) as a 32 bit guest on a 32 bit Windows 7 host. I am running VBox 4.3.12. This morning I tried to upgrade to 4.3.20, but 4.3.20 was unable to run my guest. It would go through the loading process and at the end it would die with V_ERR_MAP. I have now retreated to the safety of 4.3.12, which still works.

Actually that doesn't sound like the typical problems due to Windows hardening. I would be interested in the VBox.log as well as VBoxStartup.log file.

[Duanehebert]

I am not able to load guests created with 4.3.12 after installing this version.

When trying to open the file I get an E_INVALIDARG(0x80070057) error.


My startup log has only errors related to wintab32.dll:

13d8.c54: supR3HardenedMonitor_LdrLoadDll: error opening 'C:\Windows\system32\wintab32.dll': 0 (NtPath=\??\C:\Windows\system32\wintab32.dll; Input=C:\Windows\system32\wintab32.dll)


Is this an indication of problem caused by the added "hardening"? This file does not exist on my computer in the c:\Windows\system32 folder. Is the fact that it's missing the cause of the problem?

[gkrekelberg]

I'm upgrading from 4.3.12, installing the 4.3.20.96997 release on Windows 7 64bit.
I now can't open my Windows client. VirtualBox hangs trying to open it, displaying a small "Starting VM" popup.
It remains at stage 1 of 2 "creating process for virtual machine" at 0%.
When I try to cancel it, it doesn't respond. When I close it by the X button, 4 VirtualBox processes remain running.
When I try to kill the processes, one process keeps running that I can't kill.
This process prevents me from closing down my computer.
Help?
I'm now reverting back to 4.3.12.
[EDIT:] Using 4.3.12 I can start my VM again.