From mboxrd@z Thu Jan 1 00:00:00 1970 From: Valtteri Kiviniemi Subject: Re: xm save of upstream kernel (broken?) Date: Wed, 29 Jul 2009 03:17:46 +0300 Message-ID: <4A6F952A.5010802@dataproof.fi> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: Jeremy Fitzhardinge , "Xen-Devel (E-mail)" List-Id: xen-devel@lists.xenproject.org I have the same problem with every newer dom0 kernels, not only pv_ops. For example 2.6.30 with opensuse patches crashes the same way. - Valtteri Kiviniemi Dan Magenheimer kirjoitti: > Is "xm save" on an upstream pvops kernel supposed to > work? If so, is any special configuration required? > (I do have /proc/xen mounted... "ls /proc/xen" > shows xenbus.) > > Using xen-unstable and a PV guest with a 2.6.30 kernel, > I get "xen suspending xenbus..." in the console, > then nothing. The save file gets 1922 bytes > of data, "xm list" shows the domain as migrating-NAME > but the save never completes and I have to "xm destroy" > it. > > Booting a 2.6.18-based kernel in the same VM seems > to save/restore fine. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel