From: David Markey <admin@dmarkey.com>
To: Stephen Spector <stephen.spector@citrix.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Xen List <xen-users@lists.xensource.com>
Subject: Re: [Xen-users] Xen 4.1 Feature Request List
Date: Tue, 6 Apr 2010 20:10:12 +0100 [thread overview]
Message-ID: <g2u6894a6471004061210q775c4d05z7ffe40c69f86192@mail.gmail.com> (raw)
In-Reply-To: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net>
[-- Attachment #1.1: Type: text/plain, Size: 1161 bytes --]
Hi Stephen.
Might be a long shot, but id really like to see SPICE ported to Xen.
http://spice-space.org/
On 6 April 2010 18:41, Stephen Spector <stephen.spector@citrix.com> wrote:
> Xen Community:
>
>
>
> As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow
> (shhhh, don’t tell anyone) and I wanted to get submissions underway for Xen
> 4.1 features. I have updated the Roadmap Wiki page (
> http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen
> 4.1 features to be added. Feel free to add your ideas or send me your
> features and I will update the wiki. I also plan to update the Xen.org
> roadmap page at http://www.xen.org/products/xen_roadmap.html to be a list
> of 4.1 features tomorrow, after Xen 4.0 is announced.
>
>
>
> Thanks.
>
>
>
> *Stephen Spector*
>
>
>
> Xen.org Community Manager
>
> *T:* (772) 621-5062 | *M:* (954) 854-4257
>
> stephen.spector@xen.org
>
> http://blog.xen.org | @xen_com_mgr
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
[-- Attachment #1.2: Type: text/html, Size: 2295 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-04-06 19:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 17:41 Xen 4.1 Feature Request List Stephen Spector
2010-04-06 19:10 ` David Markey [this message]
2010-04-07 11:07 ` Re: [Xen-users] " Stefano Stabellini
2010-04-07 11:15 ` Grant McWilliams
2010-04-07 11:18 ` [Xen-devel] " Stefano Stabellini
2010-04-07 11:27 ` Pasi Kärkkäinen
2010-04-07 13:06 ` David Markey
2010-04-07 14:07 ` Re: [Xen-users] " Stefano Stabellini
2010-04-07 11:13 ` Grant McWilliams
2010-04-07 14:51 ` Pasi Kärkkäinen
2010-04-07 20:59 ` Grant McWilliams
2010-04-07 21:04 ` [Xen-users] " Pasi Kärkkäinen
2010-04-07 17:17 ` Jeremy Fitzhardinge
2010-04-07 18:07 ` Keir Fraser
2010-04-07 13:51 ` Jeff Sturm
2010-04-08 12:33 ` Fantu
2010-04-08 17:30 ` Jeremy Fitzhardinge
2010-04-08 18:23 ` Fantu
2010-04-08 18:40 ` Jeremy Fitzhardinge
2010-04-08 19:00 ` Thomas Goirand
2010-04-08 19:46 ` Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Carsten Schiers
2010-04-08 20:12 ` Pasi Kärkkäinen
2010-04-10 9:26 ` AW: " Carsten Schiers
2010-04-12 7:59 ` Pasi Kärkkäinen
2010-04-08 20:46 ` Konrad Rzeszutek Wilk
2010-04-10 16:07 ` Xen 4.1 Feature Request List Christian Tramnitz
2010-04-10 2:09 ` Vincent, Pradeep
2010-04-20 10:32 ` Juergen Gross
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=g2u6894a6471004061210q775c4d05z7ffe40c69f86192@mail.gmail.com \
--to=admin@dmarkey.com \
--cc=stephen.spector@citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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).