From: John Byrne <john.l.byrne@hp.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Stability of migration?
Date: Tue, 13 Jun 2006 17:32:52 -0700 [thread overview]
Message-ID: <448F5934.1010805@hp.com> (raw)
Hi,
With xen-unstable changset 10333:360f9dc71f51, live migration is not
reliable. Migrating an active domain (I use a kernel build in my test)
back and forth between two machines will result in the build or the
domain crashing. I tweaked xc_linux_save.c to enable the verify pass
without outputting all the debugging messages and I can see that one or
two pages do not get a data match in the log.
I have yet to see a failure of the domain with non-live migration, but I
sometimes see a data mismatch on a page during the verification. Which
would indicate that either suspend doesn't mean what I think it does or
pages of a suspended VM are being altered when they shouldn't be.
So, I guess I'll start with the easy question: should non-live migration
ever have a page fail to verify? If not, how can I identify the source
of the problem?
The harder question: how to identify the source of the corruption in
live migration?
Thanks,
John Byrne
next reply other threads:[~2006-06-14 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 0:32 John Byrne [this message]
2006-06-14 1:12 ` Stability of migration? John Byrne
2006-06-14 7:24 ` Keir Fraser
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=448F5934.1010805@hp.com \
--to=john.l.byrne@hp.com \
--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.