From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: "admin@dmarkey.com" <admin@dmarkey.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Thiago Camargo Martins Cordeiro <thiagocmartinsc@gmail.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: Porting SPICE to Xen
Date: Mon, 11 Jan 2010 11:27:21 +0000 [thread overview]
Message-ID: <4B4B0B19.1010505@eu.citrix.com> (raw)
In-Reply-To: <6894a6471001071646g558957d4u43e1c066c34e63b3@mail.gmail.com>
On 01/08/2010 12:46 AM, David wrote:
> HVM would be a good start. It would be a good way for Xen to break
> into the VDI space easily, unless there's something I haven't come
> across?
>
> As far as I understand, if the QXL driver isn't installed, it will
> fall back to standard VGA. The spice client will still be able to
> connect, but it just wont be accelerated.
>
> The spice protocol doesn't just handle graphics, but sound and USB is
> in the pipeline.
>
> The guest QXL driver is available for windows anyway, so that will be
> HVM only, I'm not sure about the status of the X guest driver.
>
I just found out about that (maybe i'm just lagging), not sure the state
either, but at least the source code is available:
http://cgit.freedesktop.org/xorg/driver/xf86-video-qxl
--
Vincent
next prev parent reply other threads:[~2010-01-11 11:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 16:50 Porting SPICE to Xen David
2010-01-06 12:25 ` Stefano Stabellini
2010-01-07 4:33 ` Thiago Camargo Martins Cordeiro
2010-01-07 11:01 ` Vincent Hanquez
2010-01-07 11:16 ` Daniel P. Berrange
2010-01-08 0:46 ` David
2010-01-11 11:27 ` Vincent Hanquez [this message]
2010-01-11 11:57 ` Daniel P. Berrange
2010-01-11 11:57 ` David
-- strict thread matches above, loose matches on Subject: below --
2010-11-30 9:40 Porting Spice " Yanjun Wu
2010-11-30 10:36 ` Stefano Stabellini
2011-04-07 10:54 Porting spice to xen ZhouPeng
2011-04-07 11:39 ` Stefano Stabellini
2011-04-08 2:13 ` ZhouPeng
2011-04-08 12:23 ` Stefano Stabellini
2011-04-09 10:27 ` ZhouPeng
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=4B4B0B19.1010505@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=admin@dmarkey.com \
--cc=berrange@redhat.com \
--cc=thiagocmartinsc@gmail.com \
--cc=xen-devel@lists.xensource.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).