From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Byrne Subject: Re: Xen 3.0.4 migration failures Date: Mon, 08 Jan 2007 11:20:53 -0800 Message-ID: <45A29995.6000903@hp.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; 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: Keir Fraser Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > On 6/1/07 12:52 am, "John Byrne" 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