From: Gerd Hoffmann <kraxel@redhat.com>
To: spice-list <spice-list@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Fedora Virtualization List <fedora-virt@redhat.com>
Subject: [Qemu-devel] spice/unstable status update.
Date: Fri, 07 May 2010 13:34:42 +0200 [thread overview]
Message-ID: <4BE3FAD2.6090503@redhat.com> (raw)
Hi folks,
Here is a short status update about what is happening in spice land.
For those which don't know yet what spice is: Spice is a remote desktop
protocol. It uses a paravirtual graphics card (qxl) for good
performance. The (slightly outdated) project website with background
information is http://www.spice-space.org/ The download section has
windows guest drivers.
Fedora packages are available from
http://kraxel.fedorapeople.org/spice/
Recommended reading:
http://kraxel.fedorapeople.org/spice/README
Latest qemu patches are available here:
http://cgit.freedesktop.org/spice/qemu/log/?h=spice.v5.1
These qemu patches depend on some spice changes not (yet) merged:
http://cgit.freedesktop.org/~kraxel/spice/log/?h=api.v5
cheers,
Gerd
reply other threads:[~2010-05-07 13:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BE3FAD2.6090503@redhat.com \
--to=kraxel@redhat.com \
--cc=fedora-virt@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-list@redhat.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).