Re: [Qemu-devel] [PATCH 22/23] gtk: show a window for each graphical QemuConsole

[Gerd Hoffmann]

  Hi,

>>>> If so, we're going to need to model what the hardware actually
>>>> does, which is that there's a single connection on the back
>>>> of the box for a monitor, and it's guest software controllable
>>>> which of the two display devices is routed to the connection...
>>>
>>> How does this work in 1.4?
>>
>> I guess the second display device was never ever shown anywhere?
> 
> Correct. We rely on "last display device wins" plus the fact this
> happens to match up with the device Linux chooses for display.
> This is obviously not great but up til now QEMU hasn't actually
> supported multiple display devices so I haven't worried about it.

Ok.

I think the most sensible way to handle this is to implement the output
routing device, make it own the (single) QemuConsole, and depending on
the router state the one or the other display device is allowed to
render to the QemuConsole.

Alternative would be to give a QemuConsole to each display device (like
it is today), then add graphics_hw_{activate,deactivate} ops and have
UIs react on it.  I suspect that would quickly become a bit messy though
with all the different UIs we have.  Also with gtk you could end up with
the vte tabs being attached to a window with an inactive display device ...

Comments?

cheers,
  Gerd