This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] xm save of upstream kernel (broken?)

To: "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] xm save of upstream kernel (broken?)
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Tue, 28 Jul 2009 16:13:11 -0700 (PDT)
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Delivery-date: Tue, 28 Jul 2009 16:13:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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"

Booting a 2.6.18-based kernel in the same VM seems
to save/restore fine.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>