Virtual screen 2 crashes after update to virtualbox 6.0.10 (#18886)

Discussions related to using VirtualBox on Windows hosts.

Virtual screen 2 crashes after update to virtualbox 6.0.10 (#18886)

Postby hagglebaggle » 31. Aug 2019, 01:56


ModEdit; related ticket: #18886: Virtual screen 2 crashes after update to virtualbox 6.0.10, but only when running ubuntu

I usually run ubuntu 18.04 in a virtual box on a Windows 10 host and use two screens, i.e. virtual screen 1 and virtual screen 2. Today I updated my virtualbox to 6.0.10. When I restart the virtual box both virtual screen 1 and virtual screen 2 starts as usual.
I can move the windows with virtual screen 1 and virtual screen 2 around. However, when I try to go to full screen or to resize the windows, screen 2 closes/crashes. It is then impossible to restart it by choosing view->virtual screen 2 -> enable. Only by restarting the virtual machine, both virtual screen starts. But as before, virtual screen 2 closes/crashes as soon as I try to change the size.

To see where the problem lies I also installed ubuntu 19.04 and windows 10 in virtual machines. With ubuntu 19.04 I still got the same problem. But with the windows 10 virtual machine everything worked, even if the graphics of window is flickering a couple of seconds before adapting to the new size. What can I do?
Last edited by socratis on 31. Aug 2019, 18:08, edited 1 time in total.
Reason: Added ticket related information.
hagglebaggle
 
Posts: 2
Joined: 31. Aug 2019, 01:26

Re: Virtual screen 2 crashes after update to virtualbox 6.0.10 (#18886)

Postby socratis » 31. Aug 2019, 18:16

Just to get the facts/terminology straight, a screen doesn't "crash" ;)

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
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 26118
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Virtual screen 2 crashes after update to virtualbox 6.0.10 (#18886)

Postby hagglebaggle » 31. Aug 2019, 19:40

Thank you for the answer and sorry for my inexact terminology :)

I followed your instructions, two times.
The first time I tried to resize the window containing virtual screen 2 by putting the mouse pointer in the bottom right corner and drag. This corresponds to “ubuntu 18.04-2019-08-31-19-22-42.log”.
The second time I tried to go to fullscreen by hitting host+f. This corresponds to “ubuntu 18.04-2019-08-31-19-26-22.log”.
The window with virtual screen 2 crashed/closed both times.

Let med know if I should provide anything else.
Attachments
ubuntu 18.04-2019-08-31-19-22-42.log.zip
(35.34 KiB) Downloaded 9 times
Last edited by socratis on 3. Sep 2019, 12:57, edited 1 time in total.
Reason: Removed unnecessary attachment, be more "green".
hagglebaggle
 
Posts: 2
Joined: 31. Aug 2019, 01:26

Re: Virtual screen 2 crashes after update to virtualbox 6.0.10 (#18886)

Postby socratis » 3. Sep 2019, 13:41

First of all, I deleted one of your two (almost identical twins) logs. There's no need to analyze two logs; twice the time/effort for me. Plus, it helps you, it helps us, it helps the server, it helps save a (virtual) tree or two... ;)

I tried to replicate your setup, and it failed, just like you're describing it. The reason? VMSVGA.
00:00:02.740832   VMSVGAEnabled      <integer> = 0x0000000000000001 (1)
00:00:02.740833 VMSVGAPciBarLayout <integer> = 0x0000000000000001 (1)
00:00:02.740833 VMSVGAPciId <integer> = 0x0000000000000001 (1)

I was asked to test a Linux guest today with 3 vScreens. So, I picked an Mint19 (based on Ubuntu18.04) and tried it. What I found was:
  • VBoxVGA: everything works as expected. Even the screensaver... ;)
  • VMSVGA: everything fails if you Enable/Disable a vScreen, or if you try to resize it, even from within the guest. The 2nd and 3rd vScreens went missing, the 1st screen reverted to a 640x480 (was 1280x1024).

    On an OSX host there's another entry, the Window menu, and even if I chose to show the 2nd and 3rd vScreen, the guest didn't realize that they were there.
Another minor observation, is the naming of the vScreens:
  • VBoxVGA: VBox 0" VGA-#
  • VMSVGA: Unknown Virtual#
Oh, and Mint19 couldn't "remember" the vScreen arrangement, it was always putting them side-by-side. What I asked for:
+---------------++-----+
| || 2 |
| |+-----+
| 1 |
| |+-----+
| || 3 |
+---------------++-----+

What Mint always reverted to, if VMSVGA was used:
+---------------++-----++-----+
| || 2 || 3 |
| |+-----++-----+
| 1 |
| |
| |
+---------------+
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 26118
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 60 guests