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


Re: [Xen-devel] c/s 18634 causing save/restore problem

To: "mukesh.rathor@xxxxxxxxxx" <mukesh.rathor@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] c/s 18634 causing save/restore problem
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 17 Jul 2009 08:03:07 +0100
Cc: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>
Delivery-date: Fri, 17 Jul 2009 00:03:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A5FDBBD.7030707@xxxxxxxxxx>
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
Thread-index: AcoGhCd0WGD9XFmJTX6JzaUAZRGVuwAKHtrT
Thread-topic: [Xen-devel] c/s 18634 causing save/restore problem
User-agent: Microsoft-Entourage/
On 17/07/2009 03:02, "Mukesh Rathor" <mukesh.rathor@xxxxxxxxxx> wrote:

> This on xen 3.4.0. We discovered that following would cause a PV guest (5u3)
> to panic:
>      - xm save guest
>      - xm restore guest
>      - xm save guest again <-- panic  in _FIRST_CPU+0X0/0X1A
> We've narrowed it down to c/s 18634. Now we're trying to find out why that
> change was made? Was that fixing some other bug?

You should cc the patch contributor where possible. In this case it is Tim
Deegan (cc'ed) and the patch looks like a straightforward and obviously
correct bug fix to me, as pretty clearly explained in the changeset comment.

Perhaps it has revealed a latent bug elsewhere?

The patch is also in 3.3.1 by the way. Have you seen problems there too?

 -- Keir

Xen-devel mailing list

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