From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant McWilliams Subject: Re: [Xen-users] Xen 4.1 Feature Request List Date: Wed, 7 Apr 2010 04:13:07 -0700 Message-ID: References: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2125944060==" Return-path: In-Reply-To: <652FFB2C8F91E3428799B1FFF8B490C9726E68A402@FTLPMAILBOX01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stephen Spector Cc: Xen-devel , Xen List List-Id: xen-devel@lists.xenproject.org --===============2125944060== Content-Type: multipart/alternative; boundary=001485e7c806bc00fd0483a3a631 --001485e7c806bc00fd0483a3a631 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Apr 6, 2010 at 10:41 AM, Stephen Spector wrote: > Xen Community: > > > > As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow > (shhhh, don=E2=80=99t tell anyone) and I wanted to get submissions underw= ay 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* > These might not be wishes for 4.1 as some may be too big but they're my wishlist anyway. Note they also might not be things that belong to the Hypervisor but rather to tools associated with. 1. Make qcow2 actually work and include backing files. 1. If it can't be made to work then it should be taken out and not mentioned in the docs so we don't waste weeks trying to get it to wor= k. 2. Figure out why you can't start a VM with a disk image residing in = a ramdisk (bug?) 3. Nesting 1. As silly as this feature sounds it may be why I leave Xen for KVM. This would be useful for teaching management of VMs. A student could have a Dom0 and start up DomUs inside it without each on needing their own physical machine. 4. Install PV DomU from CD without FTP/NFS tricks. 1. I don't care how it's done but it would be nice. The "install from network" shuffle can pose a complexity for people getting started in = Xen. I'm aware that HVM does this because of it's use of Qemu but it would= be nice everywhere. Maybe as Xen moves to Hybrid VMs instead of PV/HVM t= his will no longer be an issue. I'm sure I'll think of others but that's off the top of my head. Like I sai= d maybe some of it would be Xen 5 stuff, I don't know. --001485e7c806bc00fd0483a3a631 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Tue, Apr 6, 2010 at 10:41 AM, Stephen= Spector <stephen.spector@citrix.com> wrote:

Xen Community:

=C2=A0

As many of you are aware, the Xen 4.0 hypervisor is = due to ship tomorrow (shhhh, don=E2=80=99t tell anyone) and I wanted to get submis= sions 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.

=C2=A0

Thanks.

=C2=A0

Stephen Spector

<= div>
These might not be wishes for 4.1 as some may be too big but they&#= 39;re my wishlist anyway. Note they also might not be things that belong to= the Hypervisor but rather to tools associated with.

  1. Make qcow2 actually work and include backing files.
      2. If it can't be made to work then it should be taken out and not mentio= ned in the docs so we don't waste weeks trying to get it to work.
  2. Figure out why you can't start a VM with a disk image res= iding in a ramdisk (bug?)
  3. Nesting
    1. As silly as this feat= ure sounds it may be why I leave Xen for KVM. This would be useful for teac= hing management of VMs. A student could have a Dom0 and start up DomUs insi= de it without each on needing their own physical machine.
  4. Install PV DomU from CD without FTP/NFS tricks.
      5. =
    1. I don't care how it's done but it would be nice. The "inst= all from network" shuffle can pose a complexity for people getting sta= rted in Xen. I'm aware that HVM does this because of it's use of Qe= mu but it would be nice everywhere. Maybe as Xen moves to Hybrid VMs instea= d of PV/HVM this will no longer be an issue.

I'm sure I'll think of others but that's of= f the top of my head. Like I said maybe some of it would be Xen 5 stuff, I = don't know.
--001485e7c806bc00fd0483a3a631-- --===============2125944060== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============2125944060==--