From: Ian Campbell <Ian.Campbell@citrix.com>
To: Keir Fraser <keir.xen@gmail.com>
Cc: Tim M <bugs@linuxrehab.com>,
"xen-devel@lists.xensource.com" <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: Thu, 14 Apr 2011 07:40:08 +0100 [thread overview]
Message-ID: <1302763208.5528.36.camel@localhost.localdomain> (raw)
In-Reply-To: <C9CBBF7A.164DF%keir.xen@gmail.com>
On Wed, 2011-04-13 at 21:00 +0100, Keir Fraser wrote:
> On 13/04/2011 20:31, "Tim M" <bugs@linuxrehab.com> wrote:
> > 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.
This issue was introduced in one of the upstream longterm 2.6.32.y
kernels (by 1345126c761f in v2.6.32.16, I think). It was fixed upstream
in e7a3481c0246 "x86/pvclock: Zero last_value on resume" from
v2.6.37-rc6 which was added to the longterm 2.6.32.x branch as
595b62a8acfb in v2.6.32.30. It appears to have also gone into longterm
v2.6.35.12 as ac9a0f1a28f5.
This issue is fixed in the 2.6.32-31 package currently in Debian stable.
I can't speak for Ubuntu. You should contact them.
Ian.
next prev parent reply other threads:[~2011-04-14 6:40 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
2011-04-14 6:40 ` Ian Campbell [this message]
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=1302763208.5528.36.camel@localhost.localdomain \
--to=ian.campbell@citrix.com \
--cc=bugs@linuxrehab.com \
--cc=keir.xen@gmail.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).