From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] spice: add qxl device
Date: Thu, 18 Nov 2010 11:08:02 +0200 [thread overview]
Message-ID: <20101118090802.GE16832@redhat.com> (raw)
In-Reply-To: <4CE4E22A.6040303@redhat.com>
On Thu, Nov 18, 2010 at 09:22:02AM +0100, Gerd Hoffmann wrote:
> On 11/18/10 09:09, Gleb Natapov wrote:
> >On Wed, Nov 17, 2010 at 08:00:08PM +0200, Michael S. Tsirkin wrote:
> >>>>> If so: does qemu
> >>>>>emulate this correctly?
> >>>>
> >>>>It mostly does.
> >>>
> >>>I doubt it actually enables/disables the legacy vga ports.
> >>
> >>I'll check when I have the time. We can fix it if it doesn't,
> >>
> >So many guests (all of them?) just assume that vga ports and
> >framebuffer is there. So what "fixing" this will buy us?
>
> Nothing?
>
> Certainly not for the qemu standard vga. The only way for guests is
> to drive that one is via legacy vga ports and vesa vga bios.
> Hotplug is never ever going to work here.
> Also the vga memory window @ 0xa0000 with the piix chipset
> interactions is good for some extra fun ...
>
> cirrus might be fixable to be hotpluggable. It also can be
> programmed via mmio bar instead of legacy vga ports, so having two
> cirrus cards in one system might be possible to get work. I doubt
> it is worth the trouble though.
We will need to fix this for proper pci memory management, anyway.
> I still think that vga cards should simply be flagged to be not
> hot-pluggable.
>
> cheers,
> Gerd
Send a patch.
--
MST
next prev parent reply other threads:[~2010-11-18 9:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 13:34 [Qemu-devel] [PATCH] spice: add qxl device Gerd Hoffmann
2010-11-16 14:24 ` Anthony Liguori
2010-11-17 13:14 ` Gerd Hoffmann
2010-11-16 17:43 ` [Qemu-devel] " Michael S. Tsirkin
2010-11-17 13:28 ` Gerd Hoffmann
2010-11-17 13:58 ` Michael S. Tsirkin
2010-11-17 15:20 ` Gerd Hoffmann
2010-11-17 16:42 ` Michael S. Tsirkin
2010-11-17 17:02 ` Gerd Hoffmann
2010-11-17 18:00 ` Michael S. Tsirkin
2010-11-18 8:09 ` Gleb Natapov
2010-11-18 8:22 ` Gerd Hoffmann
2010-11-18 9:08 ` Michael S. Tsirkin [this message]
2010-11-18 10:46 ` Gerd Hoffmann
2010-11-18 9:03 ` Michael S. Tsirkin
2010-11-18 9:11 ` Gleb Natapov
2010-11-18 9:30 ` Michael S. Tsirkin
2010-11-18 9:57 ` Gleb Natapov
2010-11-18 11:33 ` Michael S. Tsirkin
2010-11-18 11:55 ` Gleb Natapov
2010-11-18 12:03 ` Michael S. Tsirkin
2010-11-18 12:27 ` Gleb Natapov
2010-11-18 14:04 ` Michael S. Tsirkin
2010-11-18 14:57 ` Gleb Natapov
2010-11-18 15:25 ` Michael S. Tsirkin
2010-11-18 15:42 ` Gleb Natapov
2010-11-18 16:04 ` Michael S. Tsirkin
2010-11-18 16:10 ` Gleb Natapov
2010-11-18 16:14 ` Michael S. Tsirkin
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=20101118090802.GE16832@redhat.com \
--to=mst@redhat.com \
--cc=gleb@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).