From: John Byrne <john.l.byrne@hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Live migration leaves page tables read-only?
Date: Wed, 29 Nov 2006 08:49:46 -0800 [thread overview]
Message-ID: <456DBA2A.7050206@hp.com> (raw)
In-Reply-To: <C192EA4D.5011%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
>
>
> On 29/11/06 2:52 am, "John Byrne" <john.l.byrne@hp.com> wrote:
>
>>> What happens if you use non-live relo?
>> I thought I had tested that way back at the beginning without seeing the
>> problem, but I must not have, because I just retested it to be sure and
>> it died the same way. (Now I am truly confused and I need to go back and
>> re-examine some of my earlier experiments.)
>>
>> In the meantime, any ideas where to look?
>
> This will be very dependent on the guest that is being migrated. What Linux
> kernel is the domU running?
>
> -- Keir
>
>
>
Linux 2.6.16.29 (+ the SLES 10 iscsi patches) with approximately the
config used by the SLES 10 Xen kernel.
I can send the config, if you need it.
John Byrne
next prev parent reply other threads:[~2006-11-29 16:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 0:13 Live migration leaves page tables read-only? John Byrne
2006-11-29 0:22 ` John Byrne
2006-11-29 1:36 ` Ian Pratt
2006-11-29 2:52 ` John Byrne
2006-11-29 7:42 ` Keir Fraser
2006-11-29 16:49 ` John Byrne [this message]
2006-11-30 23:36 ` John Byrne
2006-12-01 1:13 ` Ian Pratt
2006-12-09 5:40 ` John Byrne
2006-12-09 5:44 ` John Byrne
2006-12-09 8:33 ` Ian Pratt
2006-12-09 9:22 ` Keir Fraser
2006-12-09 9:34 ` Keir Fraser
2006-12-09 9:48 ` Keir Fraser
2006-12-11 17:00 ` Joe Bonasera
2006-12-11 18:29 ` Ian Pratt
2006-12-11 19:55 ` John Byrne
2006-12-11 21:30 ` Joe Bonasera
2007-01-14 4:11 ` John Byrne
2007-01-14 8:21 ` Ian Pratt
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=456DBA2A.7050206@hp.com \
--to=john.l.byrne@hp.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=m+Ian.Pratt@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.