From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: Xen 4.2 new features and status -- please help me make a list Date: Fri, 7 Sep 2012 17:59:42 +0200 Message-ID: <20120907155942.GA28841@aepfle.de> References: <1347027296.30018.108.camel@zakaz.uk.xensource.com> <8149449A-BB9D-40AE-945F-ACED38979F19@gmail.com> <1347032878.30018.127.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1347032878.30018.127.camel@zakaz.uk.xensource.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: Ian Campbell Cc: Andres Lagar-Cavilla , Tim Deegan , xen-devel List-Id: xen-devel@lists.xenproject.org On Fri, Sep 07, Ian Campbell wrote: > On Fri, 2012-09-07 at 15:34 +0100, Andres Lagar-Cavilla wrote: > > > > xenpaging: Page HVM guest pages to disk > > > Was marked as tech preview in 4.1 and earlier, still is? > > > > > > memsharing: Sharing of HVM guest pages. > > > Was marked as tech preview in 4.1 and earlier, still is? > > > > Both xenpaging and memsharing are functional as far as I am concerned. > > This is on the hypervisor side I guess? Or are the tools as supplied in > the xen tree useful too? xenpaging and the hypervisor work ok. The lack of xend/libxl integration causes small inconvenience because the actual memory footprint has to be set manually with xenstore-write. And until a target is set in xenstore the tool does a busyloop. This is fixed with this patch, sent a few days ago: > > Xen{paging/sharing} still have border conditions in which domains are > > crashed. They are rare enough that I have not experienced them in > > practice. This is due to a need for more mature wait queue code in the > > hypervisor. The plan is to address this in 4.3. > > Perhaps that's an argument for leaving it as tech-preview until 4.3 > then? I would say yes, at least for paging. Olaf