virtualbox.org

I can no longer get my Windows guest to span two physical monitors as 1 screen.

What changed? My monitor died this morning so I replaced it. Apparently disconnecting a monitor on an Ubuntu 14.04 host with Compiz can crash Compiz. So I had to reboot. No problem, except after the monitor exchange and reboot, when I go full screen on my Windows guest it's only on ONE monitor. I can't explain it.

I've reviewed this post and still can't make it span both monitors.

viewtopic.php?f=1&t=57693

I've reinstalled VBox Guest Editions... no change. I'm set to 2 monitors in VBox (and I was prior to this morning's problem).

My host is running fine but I want my Windows guest to span both monitors as one screen. I did manage to get Windows to go full screen by enabling the second monitor in Windows and then expanding to that second monitor in the Windows control panel settings. But the screen resolution isn't correct. AND... this is not how it worked prior to the monitor exchange.

How can I configure VBox such that Windows sees a single super wide screen instead of "expanded" in Windows conrol panel, to use two screens?

Suggestions?

I have the answer...

The monitor that failed was actually 1 of 3, so I moved the 3rd monitor to postion 1 and had 2 active monitors instead of 3. I've never gotten the 3rd one to display anything other than a white 'X' for the cursor... no display manager will load like I want... but that's a different problem. http://ubuntuforums.org/showthread.php?t=2297944

The key here is that Ubuntu thinks that 3rd monitor gives me a super-wide screen. VirtualBox thinks my max screen resolution is now 3840 x 1200. Which is EXACTLY what I had, and what I want. So the failed monitor did cause this problem in a round-about way. Now that I have my 3rd monitor restored, it still displays nothing but it does give me my desired resolution.

There was nothing wrong with VirtualBox or VBox Additions, or my settings for multiple monitors. None of it needed to change. Who would have thought a dead monitor would cause a change to VBox maximum screen resolution... even though I had enough screen real estate to support it VirtualBox wouldn't recognize it.

So this is resolved.