From: Keir Fraser <keir.xen@gmail.com>
To: Tim M <bugs@linuxrehab.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: Wed, 13 Apr 2011 19:34:01 +0100 [thread overview]
Message-ID: <C9CBAB29.164C9%keir.xen@gmail.com> (raw)
In-Reply-To: <20110413162545.GA29815@lumida.com>
On 13/04/2011 17:25, "Tim M" <bugs@linuxrehab.com> wrote:
> It was suggested that I submit this to xen-devel in addition to the bug
> report.
>
>
> I am having the exact problem described in bug 1282. The RedHat 5 errata for
> Xen 3 describes the problem nicely so I will quote it:
>
> xen calculates its running time by adding the hypervisor's up-time to the
> hypervisor's boot-time record. In live migrations of para-virtualized
> guests, however, the guest would over-write the new hypervisor's boot-time
> record with the boot-time of the previous hypervisor. This caused
> time-dependent processes on the guests to fail
>
> This bug was apparently fixed in 3.1.1
> (http://xenbits.xen.org/hg/xen-unstable.hg/rev/359707941ae8) but I am having
> the issue now with Xen 4.0.1 on Debian Squeeze.
>
> Did something change with the migrate/restore process so the previous fix no
> longer applies?
The fix is still there, albeit in a modified form since the restore code has
changed quite a bit since Xen 3. Can you reliably repro this, with any PV
guest?
-- Keir
> Thanks in advance for any help
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-04-13 18:34 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 [this message]
2011-04-13 19:31 ` Tim M
2011-04-13 20:00 ` Keir Fraser
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=C9CBAB29.164C9%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).