All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim M <bugs@linuxrehab.com>
To: Keir Fraser <keir.xen@gmail.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 12:31:57 -0700	[thread overview]
Message-ID: <20110413193156.GC6445@lumida.com> (raw)
In-Reply-To: <C9CBAB29.164C9%keir.xen@gmail.com>

On Wed, Apr 13, 2011 at 07:34:01PM +0100, Keir Fraser wrote:
> 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

This is 100% reproducible. Every time I migrate from a host with an uptime
longer than the target host, the VM has a clock/time freeze for however long
the uptime difference is. Migrating from a host with shorter uptime to a host
with longer has no problem.

As a demonstration, I have two dom0 hosts that have roughly 6 minutes
difference in uptime. I started a guest VM on the dom0 host with a longer
uptime then SSH'd to the guest and ran this command:

while true ; do date ; sleep 5 ; done

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


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.

  reply	other threads:[~2011-04-13 19:31 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 [this message]
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=20110413193156.GC6445@lumida.com \
    --to=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 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.