From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Fioravante Subject: Re: Xen 4.3 development update, and stock-taking Date: Wed, 16 Jan 2013 13:03:21 -0500 Message-ID: <50F6EB69.1060308@jhuapl.edu> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5922310921861723012==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: Ian Campbell , Wei Liu , Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , Jim Fehlig , Jan Beulich , Anthony PERARD , Daniel De Graaf , =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= List-Id: xen-devel@lists.xenproject.org This is a cryptographically signed message in MIME format. --===============5922310921861723012== Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms070508050907020208010203" This is a cryptographically signed message in MIME format. --------------ms070508050907020208010203 Content-Type: multipart/alternative; boundary="------------090400040403050904050609" This is a multi-part message in MIME format. --------------090400040403050904050609 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable On 01/16/2013 12:55 PM, George Dunlap wrote: > Below is a summary of the projects / features being worked on for the=20 > 4.3 time frame. The tentative feature freeze is scheduled for 25=20 > March, which is just over 2 months away. With that in mind, I think=20 > it's time to take stock of the development, so we know whether to ask=20 > for more help or divert resources. > > To that end, I've added a line called "prognosis", indicating the=20 > likelihood of completion in the 4.3 timeframe. For items involving=20 > code hosted on the Xen.org site (including qemu-xen), that means a=20 > likelihood of having the feature code-complete and mostly working by=20 > the feature freeze. (It's OK if there are still bugs to be worked=20 > out.) For items in Linux, I think it would mean having items on track = > to make it into the kernel released just after the scheduled 4.3 time=20 > frame. Not sure what that means for libvirt. :-) > > I've given ratings to projects that I thought I had some insight on,=20 > but I would appreciate if everyone could review these and let me know=20 > if they're not accurate. > > I'd particularly appreciate it if the people listed below could give=20 > prognoses on the project listed. > > Meanings of prognoses: > - Excellent: It would be very unlikely for this not to be finished in=20 > time. > - Good: Everything is on track, and is likely to make it. > - Fair: A pretty good chance of making it, but not as certain > - Poor: Likely not to make it unless intervention is made > - Not for 4.3: self-explanatory > > Mukesh Rathor: PVH > > Wei: Event channel scalability > > Daniel de Graaf: IS_PRIV->XSM > > Roger Pau Monne: Persistent blk grants, openvswitch integration,=20 > backend scripts > > Konrad Wilk: Persistent net grants, multi-page network, multi-page blk > > Jim Fehlig: libvirt migration support > > Matthew Fioravante: vTPM vTPM should be ready for next release, we just have one minor issue to=20 workout with the configure scripts. So I agree with your prognosis of=20 "Good". > > Stefano Panella: PV Audio > > Igor Kozhukov: IllumOS support > > Once we know what items are "at risk", we can list them and decide=20 > what to do about it. > > This information will be mirrored on the Xen 4.3 Roadmap wiki page: > http://wiki.xen.org/wiki/Xen_Roadmap/4.3 > > =3D Timeline =3D > > We are planning on a 9-month release cycle. Based on that, below are > our estimated dates: > * Feature Freeze: 25 March 2013 > * First RC: 6 May 2013 > * Release: 17 June 2013 > > The RCs and release will of course depend on stability and bugs, and > will therefore be fairly unpredictable. The feature freeze may be > slipped for especially important features which are near completion. > > =3D Feature tracking =3D > > Below is a list of features we're tracking for this release. Please > respond to this mail with any updates to the status. > > There are a number of items whose owners are marked as "?". If you > are working on this, or know who is working on it, please respond and > let me know. Alternately, if you would *like* to work on it, please > let me know as well. > > And if there is something you're working on you'd like tracked, please > respond, and I will add it to the list. > > NB: Several of the items on this list are from external projects: > linux, qemu, and libvirt. These are not part of the Xen tree, but are > directly related to our users' experience (e.g., work in Linux or > qemu) or to integration with other important projects (e.g., libvirt > bindings). Since all of these are part of the Xen community work, and > comes from the same pool of labor, it makes sense to track the > progress here, even though they won't explicitly be released as part > of 4.3. > > Meanings of prognoses: > - Excellent: It would be very unlikely for this not to be finished in=20 > time. > - Good: Everything is on track, and is likely to make it. > - Fair: A pretty good chance of making it, but not as certain > - Poor: Likely not to make it unless intervention is made > > =3D=3D Completed =3D=3D > > * Serial console improvements > -EHCI debug port > > * Default to QEMU upstream (partial) > - pci pass-thru (external) > - enable dirtybit tracking during migration (external) > - xl cd-{insert,eject} (external) > > * CPUID-based idle (don't rely on ACPI info f/ dom0) > > =3D=3D Bugs =3D=3D > > * xl, compat mode, and older kernels > owner: ? > Many older 32-bit PV kernels that can run on a 64-bit hypervisor with= > xend do not work when started with xl. The following work-around=20 > seems to > work: > xl create -p lightning.cfg > xenstore-write /local/domain/$(xl domid=20 > lightning)/device/vbd/51713/protocol x86_32-abi > xl unpause lightning > This node is normally written by the guest kernel, but for older kern= els > seems not to be. xend must have a work-around; port this=20 > work-around to xl. > > =3D=3D Not yet complete =3D=3D > > * PVH mode (w/ Linux) > owner: mukesh@oracle > status (Linux): 3rd draft patches posted. > status (Xen): RFC submitted > prognosis: Good > > * Event channel scalability > owner: wei@citrix > status: RFC submitted > prognosis: Good > Increase limit on event channels (currently 1024 for 32-bit guests, > 4096 for 64-bit guests) > > * ARM v7 server port > owner: ijc@citrix > prognosis: Excellent > status: Core hypervisor and Linux patches accepted. Tools patches=20 > submitted. > > * ARM v8 server port (tech preview) > owner: ijc@citrix > status: ? > prognosis: Tech preview only > > * NUMA scheduler affinity > critical > owner: dario@citrix > status: Patches posted > prognosis: Excellent > > * NUMA Memory migration > owner: dario@citrix > status: in progress > prognosis: Fair > > * blktap3 > owner: thanos@citrix > status: RFCs posted > prognosis: Not for 4.3 > > * Default to QEMU upstream > > Add "intel-hda" to xmexample file, since it works with 64-bit Win7/8= > - qemu-based stubdom (Linux or BSD libc) > owner: anthony@citrix > status: in progress > prognosis: ? > qemu-upstream needs a more fully-featured libc than exists in > mini-os. Either work on a minimalist linux-based stubdom with > glibc, or port one of the BSD libcs to minios. > > * Persistent grants for blk (external) > owner: roger.pau@citrix > status: Initial implementation posted > prognosis: ? > > * Persistent grants for net > owner: annie.li@citrix > status: Initial implementation posted > prognosis: ? > > * Multi-page blk rings (external) > - blkback in kernel (konrad@oracle, ?@intel) > - qemu blkback > status: Not started. > prognosis: UNKNOWN > > * Multi-page net protocol (external) > owner: ijc@citrix or annie.li@oracle > status: Initial patches posted (by Wei Liu) > expand the network ring protocol to allow multiple pages for > increased throughput > > * Scalability: 16TiB of RAM > owner: jan@suse > status: Not started > > * vTPM updates > owner: Matthew Fioravante @ Johns Hopkins > prognosis: Good > status: some patches submitted, more in progress > - Allow all vTPM components to run in stub domains for increased=20 > security > - Update vtpm to 0.7.1 from 0.5.x Say this: - New vtpm domain uses tpm_emulator 0.7.4. The old vtpmd was not upgraded, it was deprecated and removed entirely. > > * Guest EFI booting > - status: tianocore in-tree, some build problems. > prognosis: Poor. > Needs new owner. > > * libvirt/libxl integration (external) > - Update libvirt to 4.2 > status: Patch accepted > - Migration > owner: cyliu@suse (?) > status: first draft implemented, not yet submitted > prognosis: ? > - Itemize other things that need work > To begin with, we need someone to go and make some lists: > - Features available in libvirt/KVM not available in libvirt/libxl > See http://libvirt.org/hvsupport.html > - Features available in xl/Xen but not available in libvirt/Xen > > * Allow XSM to override IS_PRIV checks in the hypervisor > owner: Daniel De Graaf > status: patches against 4.3-unstable posted, awaiting approval > prognosis: Good > This makes it possible to allow some user domains limited access to > dom0-only hypercalls. This could be used to allow a user-created > toolstack domain to administer its own set of VMs instead of relying > on dom0's toolstack. > > * V4V: Inter-domain communication > owner (Xen): jean.guyader@citrix.com = > status (Xen): patches submitted > prognosis: ? > owner (Linux driver): stefano.panella@citrix > status (Linux driver): in progress > > * Wait queues for mm > owner: ? > status: Draft posted Feb 2012; more work to do. > prognosis: Poor > > * xl PVUSB pass-through for both PV and HVM guests > owner: George > status: ? > prognosis: Fair > xm/xend supports PVUSB pass-through to guests with PVUSB drivers=20 > (both PV and HVM guests). > - port the xm/xend functionality to xl. > - this PVUSB feature does not require support or emulation from Qemu.= > - upstream the Linux frontend/backend drivers. Current=20 > work-in-progress versions are in Konrad's git tree. > - James Harper's GPLPV drivers for Windows include PVUSB frontend=20 > drivers. > > * xl USB pass-through for HVM guests using Qemu USB emulation > owner: George > status: Config file pass-through submitted. > prognosis: Good > xm/xend with qemu-traditional supports USB passthrough to HVM guests = > using the Qemu emulated USB controller. > The HVM guest does not need any special drivers for this feature. > So basicly the qemu cmdline needs to have: > -usb -usbdevice host:xxxx:yyyy > - port the xm/xend functionality to xl. > - make sure USB passthrough with xl works with both qemu-traditional = > and qemu-upstream. > > * xl QXL Spice support > owner: Zhou Peng > prognosis: Fair > status: Patches against 4.3-unstable posted, awaiting approval > > * Remove hardcoded mobprobe's in xencommons > owner: ? > status: ? > prognosis: Poor. > > * openvswitch toostack integration > owner: roger@citrix > prognosis: ? > status: Sample script posted by Bastian ("[RFC] openvswitch support=20 > script") > > * Rationalized backend scripts (incl. driver domains) > owner: roger@citrix > status: patches submitted > prognosis: Good > > * Xen EFI boot > - Signature checking for dom0 kernel / initrd? > status: No owner. > prognosis: Probably not for 4.4 > > * Serial console improvements > owner: ? > status: Stalled (see below) > prognosis: Probably not for 4.4. > -xHCI debug port (Needs hardware) > -Firewire (needs hardware) > > * Make storage migration possible > owner: ? > status: none > prognosis: Probably delay until 4.4 > There needs to be a way, either via command-line or via some hooks, > that someone can build a "storage migration" feature on top of libxl > or xl. > > * Full-VM snapshotting > owner: ? > status: none > prognosis: Probably delay until 4.4 > Have a way of coordinating the taking and restoring of VM memory and > disk snapshots. This would involve some investigation into the best > way to accomplish this. > > * VM Cloning > owner: ? > status: none > prognosis: Probably need 4.4 > Again, a way of coordinating the memory and disk aspects. Research > into the best way to do this would probably go along with the > snapshotting feature. > > * xl vm-{export,import} > owner: ? > status: none > prognosis: Prob put off until 4.4 (or GSoC project) > Allow xl to import and export VMs to other formats; particularly > ovf, perhaps the XenServer format, or more. > > * Memory: Replace PoD with paging mechanism > owner: george@citrix > status: none > prognosis: Prob put off until 4.4 > > * PV audio (audio for stubdom qemu) > owner: stefano.panella@citrix > status: ? > prognosis: ? > > * IllumOS support > owner: Igor Kozhukov > status: In progress > prognosis: ? > --------------090400040403050904050609 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On 01/16/2013 12:55 PM, George Dunlap wrote:
Below is a summary of the projects / features being worked on for the 4.3 time frame.=C2=A0 The tentative feature= freeze is scheduled for 25 March, which is just over 2 months away.=C2=A0 With that in mind, I think it's time to ta= ke stock of the development, so we know whether to ask for more help or divert resources.

To that end, I've added a line called "prognosis", indicating the likelihood of completion in the 4.3 timeframe.=C2=A0 For items involving code hosted on the Xen.o= rg site (including qemu-xen), that means a likelihood of having the feature code-complete and mostly working by the feature freeze.=C2=A0 (It's OK if there are still bugs to be worked out.)=C2=A0 For items in Linux, I think it would mean having items on track to make it into the kernel released just after the scheduled 4.3 time frame.=C2=A0 Not sure what that means for libvirt. :-)

I've given ratings to projects that I thought I had some insight on, but I would appreciate if everyone could review these and let me know if they're not accurate.

I'd particularly appreciate it if the people listed below could give prognoses on the project listed.

Meanings of prognoses:
- Excellent: It would be very unlikely for this not to be finished in time.
- Good: Everything is on track, and is likely to make it.
- Fair: A pretty good chance of making it, but not as certain - Poor: Likely not to make it unless intervention is made
- Not for 4.3: self-explanatory

Mukesh Rathor: PVH

Wei: Event channel scalability

Daniel de Graaf: IS_PRIV->XSM

Roger Pau Monne: Persistent blk grants, openvswitch integration, backend scripts

Konrad Wilk: Persistent net grants, multi-page network, multi-page blk

Jim Fehlig: libvirt migration support

Matthew Fioravante: vTPM
vTPM should be ready for next release, we just have one minor issue to workout with the configure scripts. So I agree with your prognosis of "Good".

Stefano Panella: PV Audio

Igor Kozhukov: IllumOS support

Once we know what items are "at risk", we can list them and decide what to do about it.

This information will be mirrored on the Xen 4.3 Roadmap wiki page:
=C2=A0http:= //wiki.xen.org/wiki/Xen_Roadmap/4.3

=3D Timeline =3D

We are planning on a 9-month release cycle.=C2=A0 Based o= n that, below are
our estimated dates:
* Feature Freeze: 25 March 2013
* First RC: 6 May 2013
* Release: 17 June 2013

The RCs and release will of course depend on stability and bugs, and
will therefore be fairly unpredictable.=C2=A0 The feature= freeze may be
slipped for especially important features which are near completion.

=3D Feature tracking =3D

Below is a list of features we're tracking for this release. Please
respond to this mail with any updates to the status.

There are a number of items whose owners are marked as "?".=C2=A0 If you
are working on this, or know who is working on it, please respond and
let me know.=C2=A0 Alternately, if you would *like* to wo= rk on it, please
let me know as well.

And if there is something you're working on you'd like tracked, please
respond, and I will add it to the list.

NB: Several of the items on this list are from external projects:
linux, qemu, and libvirt.=C2=A0 These are not part of the= Xen tree, but are
directly related to our users' experience (e.g., work in Linux or
qemu) or to integration with other important projects (e.g., libvirt
bindings).=C2=A0 Since all of these are part of the Xen community work, and
comes from the same pool of labor, it makes sense to track the
progress here, even though they won't explicitly be released as part
of 4.3.

Meanings of prognoses:
- Excellent: It would be very unlikely for this not to be finished in time.
- Good: Everything is on track, and is likely to make it.
- Fair: A pretty good chance of making it, but not as certain
- Poor: Likely not to make it unless intervention is made

=3D=3D Completed =3D=3D

* Serial console improvements
=C2=A0 -EHCI debug port

* Default to QEMU upstream (partial)
=C2=A0- pci pass-thru (external)
=C2=A0- enable dirtybit tracking during migration (extern= al)
=C2=A0- xl cd-{insert,eject} (external)

* CPUID-based idle (don't rely on ACPI info f/ dom0)

=3D=3D Bugs =3D=3D

* xl, compat mode, and older kernels
=C2=A0 owner: ?
=C2=A0 Many older 32-bit PV kernels that can run on a 64-= bit hypervisor with
=C2=A0 xend do not work when started with xl.=C2=A0 The f= ollowing work-around seems to
=C2=A0 work:
=C2=A0=C2=A0=C2=A0 xl create -p lightning.cfg
=C2=A0=C2=A0=C2=A0 xenstore-write /local/domain/$(xl domi= d lightning)/device/vbd/51713/protocol x86_32-abi
=C2=A0=C2=A0=C2=A0 xl unpause lightning
=C2=A0 This node is normally written by the guest kernel,= but for older kernels
=C2=A0 seems not to be.=C2=A0 xend must have a work-aroun= d; port this work-around to xl.

=3D=3D Not yet complete =3D=3D

* PVH mode (w/ Linux)
=C2=A0 owner: mukesh@oracle
=C2=A0 status (Linux): 3rd draft patches posted.=C2=A0 =C2=A0 status (Xen): RFC submitted
=C2=A0 prognosis: Good

* Event channel scalability
=C2=A0 owner: wei@citrix
=C2=A0 status: RFC submitted
=C2=A0 prognosis: Good
=C2=A0 Increase limit on event channels (currently 1024 f= or 32-bit guests,
=C2=A0 4096 for 64-bit guests)

* ARM v7 server port
=C2=A0 owner: ijc@citrix
=C2=A0 prognosis: Excellent
=C2=A0 status: Core hypervisor and Linux patches accepted= =2E=C2=A0 Tools patches submitted.

* ARM v8 server port (tech preview)
=C2=A0 owner: ijc@citrix
=C2=A0 status: ?
=C2=A0 prognosis: Tech preview only

* NUMA scheduler affinity
=C2=A0 critical
=C2=A0 owner: dario@citrix
=C2=A0 status: Patches posted
=C2=A0 prognosis: Excellent

* NUMA Memory migration
=C2=A0 owner: dario@citrix
=C2=A0 status: in progress
=C2=A0 prognosis: Fair

* blktap3
=C2=A0 owner: thanos@citrix
=C2=A0 status: RFCs posted
=C2=A0 prognosis: Not for 4.3

* Default to QEMU upstream
=C2=A0> Add "intel-hda" to xmexample file, since it wo= rks with 64-bit Win7/8
=C2=A0- qemu-based stubdom (Linux or BSD libc)
=C2=A0=C2=A0 owner: anthony@citrix
=C2=A0=C2=A0 status: in progress
=C2=A0=C2=A0 prognosis: ?
=C2=A0=C2=A0 qemu-upstream needs a more fully-featured li= bc than exists in
=C2=A0=C2=A0 mini-os.=C2=A0 Either work on a minimalist l= inux-based stubdom with
=C2=A0=C2=A0 glibc, or port one of the BSD libcs to minio= s.

* Persistent grants for blk (external)
=C2=A0 owner: roger.pau@citrix
=C2=A0 status: Initial implementation posted
=C2=A0 prognosis: ?

* Persistent grants for net
=C2=A0 owner: annie.li@citrix
=C2=A0 status: Initial implementation posted
=C2=A0 prognosis: ?

* Multi-page blk rings (external)
=C2=A0- blkback in kernel (konrad@oracle, ?@intel)
=C2=A0- qemu blkback
=C2=A0 status: Not started.
=C2=A0 prognosis: UNKNOWN

* Multi-page net protocol (external)
=C2=A0 owner: ijc@citrix or annie.li@oracle
=C2=A0 status: Initial patches posted (by Wei Liu)
=C2=A0 expand the network ring protocol to allow multiple= pages for
=C2=A0 increased throughput

* Scalability: 16TiB of RAM
=C2=A0 owner: jan@suse
=C2=A0 status: Not started

* vTPM updates
=C2=A0 owner: Matthew Fioravante @ Johns Hopkins
=C2=A0 prognosis: Good
=C2=A0 status: some patches submitted, more in progress =C2=A0 - Allow all vTPM components to run in stub domains= for increased security
=C2=A0 - Update vtpm to 0.7.1 from 0.5.x
Say this:
- New vtpm domain uses tpm_emulator 0.7.4.
The old vtpmd was not upgraded, it was deprecated and removed entirely.

* Guest EFI booting
=C2=A0- status: tianocore in-tree, some build problems. =C2=A0=C2=A0 prognosis: Poor.
=C2=A0=C2=A0 Needs new owner.

* libvirt/libxl integration (external)
=C2=A0- Update libvirt to 4.2
=C2=A0=C2=A0 status: Patch accepted
=C2=A0- Migration
=C2=A0=C2=A0 owner: cyliu@suse (?)
=C2=A0=C2=A0 status: first draft implemented, not yet sub= mitted
=C2=A0=C2=A0 prognosis: ?
=C2=A0- Itemize other things that need work
=C2=A0=C2=A0 To begin with, we need someone to go and mak= e some lists:
=C2=A0=C2=A0 - Features available in libvirt/KVM not avai= lable in libvirt/libxl
=C2=A0=C2=A0=C2=A0=C2=A0 See http://libvi= rt.org/hvsupport.html
=C2=A0=C2=A0 - Features available in xl/Xen but not avail= able in libvirt/Xen

* Allow XSM to override IS_PRIV checks in the hypervisor<= br> =C2=A0 owner: Daniel De Graaf
=C2=A0 status: patches against 4.3-unstable posted, await= ing approval
=C2=A0 prognosis: Good
=C2=A0 This makes it possible to allow some user domains limited access to
=C2=A0 dom0-only hypercalls. This could be used to allow = a user-created
=C2=A0 toolstack domain to administer its own set of VMs instead of relying
=C2=A0 on dom0's toolstack.

* V4V: Inter-domain communication
=C2=A0 owner (Xen): jean.guyader@ci= trix.com
=C2=A0 status (Xen): patches submitted
=C2=A0 prognosis: ?
=C2=A0 owner (Linux driver):=C2=A0 stefano.panella@citrix=
=C2=A0 status (Linux driver): in progress

* Wait queues for mm
=C2=A0 owner: ?
=C2=A0 status: Draft posted Feb 2012; more work to do. =C2=A0 prognosis: Poor

* xl PVUSB pass-through for both PV and HVM guests
=C2=A0 owner: George
=C2=A0 status: ?
=C2=A0 prognosis: Fair
=C2=A0 xm/xend supports PVUSB pass-through to guests with= PVUSB drivers (both PV and HVM guests).
=C2=A0 - port the xm/xend functionality to xl.
=C2=A0 - this PVUSB feature does not require support or emulation from Qemu.
=C2=A0 - upstream the Linux frontend/backend drivers. Cur= rent work-in-progress versions are in Konrad's git tree.
=C2=A0 - James Harper's GPLPV drivers for Windows include= PVUSB frontend drivers.

* xl USB pass-through for HVM guests using Qemu USB emulation
=C2=A0 owner: George
=C2=A0 status: Config file pass-through submitted.
=C2=A0 prognosis: Good
=C2=A0 xm/xend with qemu-traditional supports USB passthr= ough to HVM guests using the Qemu emulated USB controller.
= =C2=A0 The HVM guest does not need any special drivers fo= r this feature.
=C2=A0 So basicly the qemu cmdline needs to have:
=C2=A0=C2=A0=C2=A0=C2=A0 -usb -usbdevice host:xxxx:yyyy =C2=A0 - port the xm/xend functionality to xl.
=C2=A0 - make sure USB passthrough with xl works with bot= h qemu-traditional and qemu-upstream.

* xl QXL Spice support
=C2=A0 owner: Zhou Peng
=C2=A0 prognosis: Fair
=C2=A0 status: Patches against 4.3-unstable posted, await= ing approval

* Remove hardcoded mobprobe's in xencommons
=C2=A0 owner: ?
=C2=A0 status: ?
=C2=A0 prognosis: Poor.

* openvswitch toostack integration
=C2=A0 owner: roger@citrix
=C2=A0 prognosis: ?
=C2=A0 status: Sample script posted by Bastian ("[RFC] openvswitch support script")

* Rationalized backend scripts (incl. driver domains)
= =C2=A0 owner: roger@citrix
=C2=A0 status: patches submitted
=C2=A0 prognosis: Good

* Xen EFI boot
=C2=A0- Signature checking for dom0 kernel / initrd?
=C2=A0status: No owner.
=C2=A0prognosis: Probably not for 4.4

* Serial console improvements
=C2=A0 owner: ?
=C2=A0 status: Stalled (see below)
=C2=A0 prognosis: Probably not for 4.4.
=C2=A0 -xHCI debug port (Needs hardware)
=C2=A0 -Firewire (needs hardware)

* Make storage migration possible
=C2=A0 owner: ?
=C2=A0 status: none
=C2=A0 prognosis: Probably delay until 4.4
=C2=A0 There needs to be a way, either via command-line o= r via some hooks,
=C2=A0 that someone can build a "storage migration" featu= re on top of libxl
=C2=A0 or xl.

* Full-VM snapshotting
=C2=A0 owner: ?
=C2=A0 status: none
=C2=A0 prognosis: Probably delay until 4.4
=C2=A0 Have a way of coordinating the taking and restorin= g of VM memory and
=C2=A0 disk snapshots.=C2=A0 This would involve some inve= stigation into the best
=C2=A0 way to accomplish this.

* VM Cloning
=C2=A0 owner: ?
=C2=A0 status: none
=C2=A0 prognosis: Probably need 4.4
=C2=A0 Again, a way of coordinating the memory and disk aspects.=C2=A0 Research
=C2=A0 into the best way to do this would probably go alo= ng with the
=C2=A0 snapshotting feature.

* xl vm-{export,import}
=C2=A0 owner: ?
=C2=A0 status: none
=C2=A0 prognosis: Prob put off until 4.4 (or GSoC project= )
=C2=A0 Allow xl to import and export VMs to other formats= ; particularly
=C2=A0 ovf, perhaps the XenServer format, or more.
=C2=A0
* Memory: Replace PoD with paging mechanism
=C2=A0 owner: george@citrix
=C2=A0 status: none
=C2=A0 prognosis: Prob put off until 4.4

* PV audio (audio for stubdom qemu)
=C2=A0 owner: stefano.panella@citrix
=C2=A0 status: ?
=C2=A0 prognosis: ?

* IllumOS support
=C2=A0 owner: Igor Kozhukov
=C2=A0 status: In progress
=C2=A0 prognosis: ?


--------------090400040403050904050609-- --------------ms070508050907020208010203 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIDyjCC A8YwggMvoAMCAQICBD/xyf0wDQYJKoZIhvcNAQEFBQAwLzELMAkGA1UEBhMCVVMxDzANBgNV BAoTBkpIVUFQTDEPMA0GA1UECxMGQklTRENBMB4XDTEwMDYxMTE4MjIwNloXDTEzMDYxMTE4 NTIwNlowZjELMAkGA1UEBhMCVVMxDzANBgNVBAoTBkpIVUFQTDEPMA0GA1UECxMGUGVvcGxl MTUwFgYDVQQLEw9WUE5Hcm91cC1CSVNEQ0EwGwYDVQQDExRNYXR0aGV3IEUgRmlvcmF2YW50 ZTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAnpbwVSP6o1Nb5lcW7dd3yTo9iBJdi7qz 4nANOMFPK7JOy5npKN1iiousl28U/scUJES55gPwAWYJK3uVyQAsA4adgDKi5DoD1UHDQEwp bY7iHLJeq0NPr4BqYNqnCFPbE6HC8zSJrr4qKn+gVUQT39SIFqdiIPJwZL8FYTRQ/zsCAwEA AaOCAbYwggGyMAsGA1UdDwQEAwIHgDArBgNVHRAEJDAigA8yMDEwMDYxMTE4MjIwNlqBDzIw MTIwNzE3MjI1MjA2WjAbBg0rBgEEAbMlCwMBAQEBBAoWCGZpb3JhbWUxMBsGDSsGAQQBsyUL AwEBAQIEChIIMDAxMDQyNjEwWAYJYIZIAYb6ax4BBEsMSVRoZSBwcml2YXRlIGtleSBjb3Jy ZXNwb25kaW5nIHRvIHRoaXMgY2VydGlmaWNhdGUgbWF5IGhhdmUgYmVlbiBleHBvcnRlZC4w KAYDVR0RBCEwH4EdTWF0dGhldy5GaW9yYXZhbnRlQGpodWFwbC5lZHUwUgYDVR0fBEswSTBH oEWgQ6RBMD8xCzAJBgNVBAYTAlVTMQ8wDQYDVQQKEwZKSFVBUEwxDzANBgNVBAsTBkJJU0RD QTEOMAwGA1UEAxMFQ1JMNTYwHwYDVR0jBBgwFoAUCDUpmxH52EU2CyWmF2EJMB1yqeswHQYD VR0OBBYEFO6LYxg6r9wHZ+zdQtBHn1dZ/YTNMAkGA1UdEwQCMAAwGQYJKoZIhvZ9B0EABAww ChsEVjcuMQMCBLAwDQYJKoZIhvcNAQEFBQADgYEAJO9HQh4YNChVLzuZqK5ARJARD8JoujGZ fdo75quvg2jXFQe2sEjvLnxJZgm/pv8fdZakq48CWwjYHKuvIp7sDjTEsQfo+y7SpN/N2NvJ WU5SqfK1VgYtNLRRoGJUB5Q1aZ+Dg95g3kqpyfpUMISJL8IKVLtJVfN4fggFVUYZ9wwxggGr MIIBpwIBATA3MC8xCzAJBgNVBAYTAlVTMQ8wDQYDVQQKEwZKSFVBUEwxDzANBgNVBAsTBkJJ U0RDQQIEP/HJ/TAJBgUrDgMCGgUAoIHLMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJ KoZIhvcNAQkFMQ8XDTEzMDExNjE4MDMyMVowIwYJKoZIhvcNAQkEMRYEFJ4101GqO5PZi6yV y2OkCEfBG3NLMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAK BggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYI KoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEgYB9wT0sH0BgsagydC8ZcDpJvN+BMrdSa5gT pYfhsNv6/VhYLtyymGkWGR8Rj9iF3qfBiXeuG+4Nz3fbMLUXbn1H9eBB2fnNV3X4dv6zmUXk jYLDxqqk5faisyGxiN1yYceX5kvp+kV9tmL/FiiKhZJ4s3lVcj/dc9JlZ3vr8oERGwAAAAAA AA== --------------ms070508050907020208010203-- --===============5922310921861723012== 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.xen.org http://lists.xen.org/xen-devel --===============5922310921861723012==--