Blue screen inside guest on window resizing

[Roel]

Using Tunnelier (​http://www.bitvise.com/tunnelier) within a XP [OBI] guest running within a Windows 7 host. Resized a terminal window by using ALT-TAB twice. On the second ALT-TAB, the guest blue screened on ~ VBoxDisp.

[Roel]

A better synopsis would be "Blue screen inside guest OS (XP) on resizing of a Tunnelier terminal window, while running Tunnelier inside a guest"

[Roel]

It can be repeated.

Key sequence is not 2x ALT-TAB but 2x ALT-ENTER.

First ALT-ENTER re-sizes the terminal window, second blacks out the screen and shows a red pixelated (i.e. erroneous) banner at the top - the same as you may see when you would set a screen to too high a resolution.

When you then use vbox guest control to set the screen to "fullscreen" - you can observe the actual blue screen.

Looks easy to reproduce using the Tunnelier software. Working with fullscreen or seamless mode may help.

[Frank Mehnert]

Any reason that you are still using VBox 4.1.0 and not 4.1.6?

[sunlover]

This is most likely the same problem as ticket 9636. Fixed in 4.1.4, you have to update the guest additions.

[Roel]

Using 4.1.6 + 4.1.6 guest additions, it is not possible to blue screen the guest anymore. It is however still possible to make the guest GUI unresponsive to input + display the pixelated banner by switching between full screen, seamless and scale mode a few times. At least it does not crash the OS anymore, but it does take away GUI usability. The fact that the OS can still be shutdown (using the 'sent the shutdown signal' option) shows that the guest OS is still responsive underneath.

[Roel]

Btw, having used the vbox gui in a secondary screen in the past doesn't help with some of the screen modes. Even though only one screen is enabled in the OS now, when swapping between screen modes it seems to scale open (talking about the windows open window gui effect here) to the second screen.

[Frank Mehnert]

Sounds to me like some problem with the Guest Additions (guest control is a different thing). Please attach a VBox.log file of such a VM session.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.