From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Thiago Camargo Martins Cordeiro <thiagocmartinsc@gmail.com>
Cc: David <admin@dmarkey.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: Porting SPICE to Xen
Date: Thu, 07 Jan 2010 11:01:39 +0000 [thread overview]
Message-ID: <4B45BF13.1070901@eu.citrix.com> (raw)
In-Reply-To: <6b7f6eb1001062033v3f80ae52t5d8b590e9d7819cc@mail.gmail.com>
On 01/07/2010 04:33 AM, Thiago Camargo Martins Cordeiro wrote:
> If this happen, it will work with paravirtualized domUs too? Or maybe
> it is only for HVM domains?!
SPICE is 2 differents parts, the part that expose the PCI device to the
guest and "replace" the graphic card IIRC, and the actual remote desktop
protocol.
at the moment the 2 are fairly intertwined, so it would only work with
HVM domains [1], but depending on how the things get de-intertwined
(which is something qemu people want), it might be possible to have it
on PV. I wouldn't hold my breath on PV domain though.
(I'm no SPICE expert however, so it take it with a grain of salt.)
[1] providing all the pieces are available upstream in qemu etc.. which
probably going to take a while too.
--
Vincent
next prev parent reply other threads:[~2010-01-07 11:01 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 [this message]
2010-01-07 11:16 ` Daniel P. Berrange
2010-01-08 0:46 ` David
2010-01-11 11:27 ` Vincent Hanquez
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=4B45BF13.1070901@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=admin@dmarkey.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).