From: Dan Magenheimer Subject: RE: pv 2.6.31 (kernel.org) and save/migrate Date: Fri, 6 Nov 2009 16:08:26 -0800 (PST) Message-ID: References: <20091106223046.GA1434@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20091106223046.GA1434@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 02:27:27PM -0800, Dan Magenheimer wrote: > > > 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 > >=20 > > 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.) > >=20 > > Trying to reproduce on a different machine, just to verify. >=20 > There shouldn't be any .config changes needed. >=20 > Can you paste the full domU console output? Does it crash or?=20 >=20 > -- Pasi Well, first, I got 2.6.31.5 to boot in a PV guest in another machine and it fails to save also. Are you able to save 2.6.31{,.5} successfully? On latest xen-unstable? (NOTE: Yes, I do have CONFIG_XEN_SAVE_RESTORE=3Dy... don't know if that is important.) (On the machine I couldn't boot 2.6.31.5 as a PV guest, there was absolutely no console output. However, I think tools are out-of-date on that machine so ignore that.)