qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] all vga: refuse hotplugging.
Date: Wed, 26 May 2010 15:39:33 +0200	[thread overview]
Message-ID: <4BFD2495.6040307@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1005261411090.25605@kaball-desktop>

   Hi,

>> I think having two gfx screens mapped to two qemu consoles, then be able
>> to switch between them via Ctrl-Alt-<nr>  (like you switch today to text
>> consoles) could be doable without too much effort.  Question is how
>> useful this would be as you can't see your two screens at the same time.
>
> Actually I was thinking of registering multiple graphic consoles, each
> of them could be rendered by a different frontend (sdl/vnc)
> independently. We would have multiple DisplayStates for that.

Possible, but certainly alot of work.  Tons of code in qemu can't handle 
multiple DisplayStates.  Try it and you'll see.

>> With qxl+spice the spice client will open a new window for the secondary
>> display.  With vnc+sdl you'll see the primary display only.
>
> So you are doing exactly what I wrote above, right?

No.  The secondary display has no DisplayState.  That is the reason why 
only the spice client will see it.

cheers,
   Gerd

  reply	other threads:[~2010-05-26 13:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26  8:43 [Qemu-devel] [PATCH] all vga: refuse hotplugging Gerd Hoffmann
2010-05-26 10:59 ` Stefano Stabellini
2010-05-26 11:22   ` Gerd Hoffmann
2010-05-26 11:49     ` Stefano Stabellini
2010-05-26 12:58       ` Gerd Hoffmann
2010-05-26 13:18         ` Stefano Stabellini
2010-05-26 13:39           ` Gerd Hoffmann [this message]
2010-05-28 14:21 ` Paul Brook
2010-05-31  8:48   ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BFD2495.6040307@redhat.com \
    --to=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).