From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Magenheimer Subject: RE: pv 2.6.31 (kernel.org) and save/migrate Date: Fri, 6 Nov 2009 14:27:27 -0800 (PST) Message-ID: References: <20091106203720.GZ1434@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1252 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: =?UTF-8?B?IlBhc2kgS8Okcmtrw6RpbmVuIg==?= Cc: "Xen-Devel (E-mail)" List-Id: xen-devel@lists.xenproject.org > On Fri, Nov 06, 2009 at 10:37:49AM -0800, Dan Magenheimer wrote: > > Sorry for another possibly stupid question: > >=20 > > 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? > >=20 > > I'd assume migrate and live migrate would fail also but > > haven't tried them. > >=20 >=20 > Just checking.. are you running the latest 2.6.31.5 ? I think=20 > there has > been multiple xen related bugfixes in the 2.6.31.X releases. >=20 > -- Pasi No it was plain 2.6.31. But I downloaded/built 2.6.31.5 and can't even get it to boot (and no console or VNC output at all). Are CONFIG changes required betwen 2.6.31 and 2.6.31.5 for Xen? (I checked and I am using the same .config.) Trying to reproduce on a different machine, just to verify. Dan