From: Keir Fraser <keir.xen@gmail.com>
To: Tim M <bugs@linuxrehab.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [Bug 1759] Xen 4.0.1 live migration/restore over-writes new hypervisor's boot-time record
Date: Wed, 13 Apr 2011 21:00:42 +0100 [thread overview]
Message-ID: <C9CBBF7A.164DF%keir.xen@gmail.com> (raw)
In-Reply-To: <20110413193156.GC6445@lumida.com>
On 13/04/2011 20:31, "Tim M" <bugs@linuxrehab.com> wrote:
> Next I initiated a live migration and this is what the output of the command
> looks like (with commentary added):
>
> Wed Apr 13 12:07:48 PDT 2011
> Wed Apr 13 12:07:53 PDT 2011
> Wed Apr 13 12:07:58 PDT 2011
> Wed Apr 13 12:08:03 PDT 2011 [ migration happens here and SSH to the guest
> "freezes" for about 6 min ]
> Wed Apr 13 12:13:55 PDT 2011
> Wed Apr 13 12:14:00 PDT 2011
> Wed Apr 13 12:14:05 PDT 2011
Looks like the wallclock is correct after the migration however, and it's
that that the patch you referred to was fixing.
> I have only tried Ubuntu 10.04.2 guests running the 2.6.32 and 2.6.35 server
> kernel packages but, as mentioned, this happens every time.
I think this is a domU kernel bug, see a similar report here for example:
http://lists.xensource.com/archives/html/xen-devel/2010-10/msg00057.html
So it could be a common symptom in a range of Debian/Ubuntu kernels.
-- Keir
next prev parent reply other threads:[~2011-04-13 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 16:25 [Bug 1759] Xen 4.0.1 live migration/restore over-writes new hypervisor's boot-time record Tim M
2011-04-13 18:34 ` Keir Fraser
2011-04-13 19:31 ` Tim M
2011-04-13 20:00 ` Keir Fraser [this message]
2011-04-14 6:40 ` Ian Campbell
2011-04-14 20:44 ` Tim M
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=C9CBBF7A.164DF%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=bugs@linuxrehab.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).