From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Xen 4.3 development update Date: Fri, 21 Sep 2012 12:07:46 +0100 Message-ID: <505C4A82.2040305@eu.citrix.com> References: <201209191918.35305.hahn@univention.de> <201209201340.52218.hahn@univention.de> <505B88A1.1070701@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <505B88A1.1070701@suse.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jim Fehlig Cc: "xen-devel@lists.xen.org" , Philipp Hahn List-Id: xen-devel@lists.xenproject.org On 20/09/12 22:20, Jim Fehlig wrote: > Chun Yan Liu was working on a patch to implement migration in the libvirt libxl > driver, but she wasn't able to finish tidying the patch before departing on > maternity leave. She recently returned to work and I'd expect a refreshed patch > soon - after working through her backlog. > > But why is libvirt integration listed as a Xen 4.3 feature? AFAIK, all of this > work is in libvirt and really doesn't have much to do with the release of 4.3. For one, as Ian said, we want xl/libxl to be the default toolstack in 4.3; as soon as possible we want to remove xend. But from a broader perspective, the idea is for the Xen.org community to be thinking strategically about the success of the Xen project as a whole. Things like distro support and libvirt integration are absolutely critical to Xen's success in the open-source ecosystem. So while we don't have to do everything ourselves, we want to think about what things need to be done, track them to make sure that *someone* does them; and be prepared to pick them up ourselves if necessary. And it just makes more sense to track everything on one list. Does that make sense? -George