Page 1 of 2

Discuss the 6.0.6 release

Posted: 16. Apr 2019, 22:55
by michael
Discuss the 6.0.6 release here.
You can download the release here.
VirtualBox 6.0.6 is a new maintenance release.

VirtualBox 6.0.14 has been released. Please try that before continuing the discussion in this thread.

Known new issues/regressions
These are new and confirmed tickets about issues with 6.0.6: See also:

Re: Discuss the 6.0.6 release

Posted: 17. Apr 2019, 06:38
by Etepetete
A huge thanks to the developers!

VBox 6.0.6 installed flawlessly, and works like a charm.
GuestAdditions compiled as expected.
No issues with shared folder
No issues with audio or video playback.
No complaints whatsoever.
Great job!

Re: Discuss the 6.0.6 release

Posted: 17. Apr 2019, 09:23
by michael
Thank you!

Re: Discuss the 6.0.6 release

Posted: 17. Apr 2019, 10:21
by mpack
Found a bug within 30 seconds, perhaps a new record for me... :) I'm not sure if this is a new one or not.

Win7 64bit guest, v6.0.6 GAs installed in safe mode so that OpenGL will work, VBoxVGA graphics.

I ran an OpenGL 3D viewer in the guest, worked fine. Closed it.
Win7 guest.png
Win7 guest.png (70.23 KiB) Viewed 11665 times
I then tested whether the VM fullscreen window size restore bug had been fixed (it had), but while in fullscreen mode I ran the 3D viewer app again. The entire screen went black except for the contents of the viewer window - which had no window frame or caption bar. I had to guess where the close (X) button was to restore my guest desktop.

I tried to capture a screenshot to show you what I meant, but the screenshot captured the opposite: a visible desktop and an empty (black) OpenGL viewer window frame. While trying to get the screenshot the screen suddenly fixed itself, but broke again when I moved the viewer window.

I can't test other graphics chipsets since AFAIK none yet support OpenGL in a Windows guest.

Windows 10 Guest Performance.

Posted: 17. Apr 2019, 18:56
by isgdre
I recommend trying 6.0.6 for any user that was having performance problems on their Windows 10 Guest.

Just updated from 6.0.4 to 6.0.6 and there is a huge difference. Close to native speeds now.

Re: Discuss the 6.0.6 release

Posted: 17. Apr 2019, 21:20
by socratis
@isgdre
Merged your post with the "Discuss the 6.0.6 release".
I'm sure the devs will be glad to hear your assessment! ;)

Re: Discuss the 6.0.6 release

Posted: 18. Apr 2019, 08:50
by misvin
VirtualBox 6.0.6 Bugs (Windows 10 1809 64-bit Host):
1. Deleting a snapshot doesn't show estimated time and operation progress bar always starts from 99%.
This is a maintenance release. The following items were fixed and/or added:
[...]
User interface: fixed operation progress when deleting snapshots
2. The Search function of the .chm help does not work.

Re: Discuss the 6.0.6 release

Posted: 19. Apr 2019, 01:24
by mcp
I lose the mouse when I switch to seamless mode. And yes I did install the extensions.
How can I solve this problem?

MCP

UPDATE: I found the setting that needed to be changed. All is good now.

Re: Discuss the 6.0.6 release

Posted: 19. Apr 2019, 02:04
by socratis
@mcp, you should know what the "Minimum information needed for assistance" is. And we need to see a complete VBox.log, from a complete VM run, where the problem occurs:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
  • Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
Image

Re: Discuss the 6.0.6 release

Posted: 19. Apr 2019, 12:00
by arQon
I'm seeing kernel panics 100% of the time on shutdown. W7x64 host, ubuntu 16.04 guest with 4.4.0-145-generic.
An 18.04 guest with kernel 4.15.0-47 that's still on the 6.04 GAs doesn't have this problem.

On startup i'm sometimes seeing this as an xmessage:
VBoxClient: VBoxClient (seamless): failed to start. Stage: Setting guest IRQ filter mask Error: VERR_INTERNAL_ERROR
and shared folders aren't present. (mounted in rc.local rather than as vbox auto-mounts).

Have reinstalled the GAs a couple of times, no change.

The 4.4.0-142 kernel (the last one with working GAs in 6.04 following a signature change) exhibits the same problem with the 6.06 GAs.

add> The same VM works fine if updated to 4.15, so the problem is specific to 6.06 and 4.4 kernels. (well, probably several other old kernel versions as well, but meh)

Re: Discuss the 6.0.6 release

Posted: 19. Apr 2019, 19:13
by markos2680
Left mouse button works like right mouse button on desktop while "Input/Mouse Integration" is checked
Uncheck the "Input/Mouse Integration" solves the problem

Host : Ubuntu 18.04.2 x64, Kernel 4.18.0-16-generic
Guests tested : Windows 2003 Server, Windows 7 Pro x64
Environment : VBox 6.0.6 r130049 ( Qt 5.6.1 )

Re: Discuss the 6.0.6 release

Posted: 19. Apr 2019, 22:01
by socratis
mcp wrote:UPDATE: I found the setting that needed to be changed. All is good now.
@mcp,
Please don't leave the solutions hidden. Please make yourself clear and post the solution. What setting did you find?

Re: Discuss the 6.0.6 release

Posted: 23. Apr 2019, 10:26
by ciamaulex
Thanks for the awesome release!
This is not only more stable, but also blazing fast.

One note though: the "restore frozen at 97%" seemed completely gone.
Only once I got it again on my WinXP guest. Then I discarded the saved state and did a fresh boot, and the machine paused because it could not lock the required amount of memory.

May there be a remaining case when the "saved state restore" crashes instead of gracefully pausing the machine in low-memory conditions?

I will try to test again, in case I will send you the logs.

Best regards

Re: Discuss the 6.0.6 release

Posted: 23. Apr 2019, 10:41
by socratis
@ciamaulex
Take a look at the corresponding ticket "Win7 in VB 6.0.0 fails on resume on 97%". See comment #9 from "bird" (emphasis mine):
Seems some device is raising interrupts while restoring saved state, which it is absolutely not supposed to do, thus the release assertion later in the restore process. However, to move on with this I've degraded the release assertion to a scary log entry (in VBox.log) and we'll try hunt down the real culprit internally.

The fix will appear in 6.0.8, 5.2.30 and any test build with revision 130145 or higher. (No, we did not knowingly fix this in 6.0.6.)

Re: Discuss the 6.0.6 release

Posted: 24. Apr 2019, 09:11
by vesa
I had some problems with 6.0.6 so I could not upgrade.
* could not move around windows
* could not click on menu item in Idea
I have Windows 10 host and Ubuntu 18 guest.