All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Byrne <john.l.byrne@hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Xen 3.0.4 migration failures
Date: Mon, 08 Jan 2007 11:20:53 -0800	[thread overview]
Message-ID: <45A29995.6000903@hp.com> (raw)
In-Reply-To: <C1C52738.6C85%Keir.Fraser@cl.cam.ac.uk>

Keir Fraser wrote:
> On 6/1/07 12:52 am, "John Byrne" <john.l.byrne@hp.com> 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

      reply	other threads:[~2007-01-08 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-06  0:52 Xen 3.0.4 migration failures John Byrne
2007-01-06 10:15 ` Keir Fraser
2007-01-08 19:20   ` John Byrne [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45A29995.6000903@hp.com \
    --to=john.l.byrne@hp.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.