- I have OSX 10.9.5 on a MBP8,3 with an ATI 6750m.
You have OSX 10.12.4 on a MBP11,5 with an ATI R9 M370X. - One key, essential difference is that you boot your VM directly at full-screen, whereas I don't. You have the following in your log, at the very 1st second of the VM's creation. I noticed however, that only one message like that exists, for window #0, but nothing for window #1:
00:00:01.009049 GUI: UIMachineLogicFullscreen::sltHandleNativeFullscreenWillEnter: \ Machine-window #0 will enter native fullscreen
- After that, and due to the initial FullScreen state, here's where all the fun begins. In my case I receive a couple of "UIMachineViewNormal" events and you receive "UIMachineWindowFullscreen". The thing that I don't really feel good about is that you also log a couple of "UIMultiScreenLayout::update: GUI/AutomountGuestScreens is disabled" from the get go, while I, only when I actually switch to FullScreen. Maybe it's a red herring, I don't know.
- Launch the Mint VM with two displays, after I've already installed the matching GAs. It defaulted with both of them in one monitor, the primary one. Initial size is 800x600 for both of the displays, but this has been happening for a few VirtualBox versions now (randomly really). I even believe it was in the release notes:
- Only when I login, does display #1 goes to 1280x1024 (my favorite, previously setup size), and display #2 goes at 1024x768. I didn't even bother to configure display #2, it just "felt" that 1024x768 was the appropriate size. I then moved display #2 to the top-right corner of monitor #2. Note that I opened up a Terminal, which I chose to be half to the left and half to the right of the Mint displays (if you're wondering, the command in the Terminal is 'uname -a') :
- I hit HostKey-F. Both displays maximized to their respective monitor sizes; 1920x1280 for display #1, 1280x1024 for display #2. NOTE: Since I didn't configure the relative geometrical location of the two monitors in Mint, the two monitors are now top-aligned, as opposed to center-aligned in my native OSX setup (I had to re-align them in Gimp) :
- I hit HostKey-F to get out of FullScreen mode. I shut down the VM.
- BTW, if I hit the FullScreen Widget on display #1, here's what I end up with. Not quite what' you'd "think" it would do, but it turns out that this is standard behavior (and expected if you think about it). Only that specific window (display #1) goes to its own space, not all of the "related" windows. It's like if you have multiple Safari windows and you maximize one of them to its own space, you wouldn't expect all your Safari windows to occupy their own unique space, would you? Maybe this is what's happening in your case, and display #2 is still in its primary space? Or somewhere "lost in space"? (pun intended)
- Try to start the VM without it being in FullScreen mode.
- Move the 2nd display in the 2nd monitor before going FullScreen.
- Try with the HostKey-F combination instead of hitting the full screen OSX widget.
Side discovery
I really don't know why you have the following (I don't) or how I can change my setup to match yours. Not that it matters for your specific problem, it's a quite interesting question to me, because there is no instance of those two entries in any of my logs for any of my VMs (4 logs x ~30 VMs).
00:00:01.024694 [/Devices/ahci/0/LUN#0/Config/] (level 5) 00:00:01.024695 BlockCache <integer> = 0x0000000000000001 (1) 00:00:01.024696 Format <string> = "VDI" (cb=4) 00:00:01.024696 Mountable <integer> = 0x0000000000000000 (0) 00:00:01.024697 Path <string> = "/Users/nick/VirtualBox VMs/Mint/Mint.vdi" (cb=41) 00:00:01.024698 Type <string> = "HardDisk" (cb=9) 00:00:01.024698 UseNewIo <integer> = 0x0000000000000001 (1)