From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: pv 2.6.31 (kernel.org) and save/migrate Date: Fri, 06 Nov 2009 16:19:51 -0800 Message-ID: <4AF4BD27.1060402@goop.org> References: <20091106203720.GZ1434@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20091106203720.GZ1434@reaktio.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: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Dan Magenheimer , "Xen-Devel (E-mail)" List-Id: xen-devel@lists.xenproject.org On 11/06/09 12:37, Pasi K=E4rkk=E4inen wrote: > On Fri, Nov 06, 2009 at 10:37:49AM -0800, Dan Magenheimer wrote: > =20 >> Sorry for another possibly stupid question: >> >> I've observed that for a pv domain that's been updated >> to a 2.6.31 kernel (straight from kernel.org), "xm save" >> never completes. When the older kernel (2.6.18) >> is booted, "xm save" works fine. Is this a known problem... >> or perhaps xm save has never worked with an upstream pv >> kernel and I've never noticed? >> >> I'd assume migrate and live migrate would fail also but >> haven't tried them. >> >> =20 > Just checking.. are you running the latest 2.6.31.5 ? I think there has > been multiple xen related bugfixes in the 2.6.31.X releases. > =20 Nothing relating to save/restore. Does it work for you? J