WARNING - OLD ARCHIVES

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/
Xen

xen-devel

[Top] [All Lists]

Re: [Xen-devel] Xen 3.0.4 migration failures

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 3.0.4 migration failures
From: John Byrne <john.l.byrne@xxxxxx>
Date: 2007年1月08日 11:20:53 -0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: 2007年1月08日 11:20:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1C52738.6C85%Keir.Fraser@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C1C52738.6C85%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.9 (X11/20061206)
Keir Fraser wrote:
On 6/1/07 12:52 am, "John Byrne" <john.l.byrne@xxxxxx> wrote:
With the Xen 3.0.4 I've built from source, migration is failing and the
domain vanishes. (Either live/non-live.) The output from "xm dmesg" and
xend.log follows. Any ideas?
PAE or 64-bit? Looks like the target is choking on _PAGE_NX. Probably the
target machine does not support it. We discussed silently dropping _PAGE_NX
on machines that don't support it but that seems a bit dubious to me. This
really needs to be solved by adding CPUID to the save format and doing
consistency checking at the target before committing to the migration. 3.0.5
will also have save/restore cancellation, so that at least if things do
screw up your guest won't /dev/null.
 -- Keir
PAE. NX was disabled int the BIOS. Things work now. Thanks.
Getting rid of the "disappearing domain" issue will certainly be good, but mysterious refusals to migrate with unhelpful error messages will only be relatively better. Decent diagnostics for CPU incompatibilities are really important.
Thanks again,
John Byrne
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: Re: [Xen-devel] Building broken with CS 13282 , John Levon
Next by Date: [Xen-devel] xen test results on Unisys ES7000 - domVT shutdown is broken- results in dom0 panic , Krysan, Susan
Previous by Thread: Re: [Xen-devel] Xen 3.0.4 migration failures , Keir Fraser
Next by Thread: Re: [Xen-devel] [PATCH] Improve information displayed by the xm sched-credit command , Emmanuel Ackaouy
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /