id	summary	reporter	owner	description	type	status	component	version	resolution	keywords	cc	guest	host
16059	Unpaused hidden vms are crashing in i3-wm when removing host-screen	1337		"I'm running virtualbox on archlinux with the i3 window manager (all installed via pacman). Furthermore I'm working with two monitors on my host, thus using two screen outputs.  Since updating virtualbox from version 5.0.22-1 to 5.1.6-1 (i3-wm stood in newest available verion 4.11-1) the following error was introduced:

If I store the virtual-guest GUI-representations in an tabbed i3-container (thus only the guest behind the active tab is displayed and the other ones are kept hidden behind their tabs) and remove one of my two outputs via „xrandr --output <OUTPUT> --off“, i3 (as always) starts to merge all workspaces to the remaining monitor. Unfortunately all vms which were awake and hidden behind a inactive (meaning not displayed) i3 tab are crashed afterwards. 

The logfiles carry no information about the crashing reason, meaning both, the crashed and survived ones, whose which moved (or had to be moved) to another output and those which stayed (or should have stayed) on the remaining one, they all contain this lines in their logfile:

00:02:03.886456 GUI: UIMachineLogic: Host-screen count changed
00:02:04.014195 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:02:04.014233 GUI: UIMachineLogic: Host-screen available-area changed
00:02:04.045512 GUI: UIMachineLogic: Host-screen geometry changed
00:02:04.045641 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:02:04.045655 GUI: UIMachineLogic: Host-screen available-area changed

Is there a way to tune the logging amount for this purpose? Here is my output of

vboxmanage debugvm testvm show logdbg-settings    
Debug logger settings:
                    VBOX_LOG=all=0x0
              VBOX_LOG_FLAGS=enabled unbuffered uself overwrite abs hex
  

One possible workaround is to pause all vms, another is to keep all vms visible on a focused workspace while removing one output. Furthermore while working with two monitors the workspaces can be moved between them without causing a crash of the hidden and unpaused vms.

This is a quite strange but easy reproducible behavior. For testing purposes I set up new vms without virtual HDs just running into BIOS-settings and they crashed too.

Could be related to: https://www.virtualbox.org/ticket/15863 
"	defect	new	GUI	VirtualBox 5.1.6				all	Linux