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 14:58:19 +0200	[thread overview]
Message-ID: <4BFD1AEB.1080908@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1005261242590.25605@kaball-desktop>

   Hi,

>> Yes.  Assuming the virtual hardware in question can actually act as
>> secondary, i.e. is fully programmable without the legacy vga ports.  The
>> standard vga can't.  The cirrus looks doable, at least you can access
>> the vga ports using the mmio bar.
>
> I see, good point.
>
> I guess the right fix here would be to return -1 in the stdvga case but
> continue in the cirrus case and avoid registering the vga ioports when
> used as secondary adapter.

Except that this most likely is a non-trivial effort as we have to find 
and test sane ways to handle multiple guest displays.

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.

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.

cheers,
   Gerd

  reply	other threads:[~2010-05-26 12:58 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 [this message]
2010-05-26 13:18         ` Stefano Stabellini
2010-05-26 13:39           ` Gerd Hoffmann
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=4BFD1AEB.1080908@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).