xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tim M <bugs@linuxrehab.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Keir Fraser <keir.xen@gmail.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 13:44:48 -0700	[thread overview]
Message-ID: <20110414204448.GD6445@lumida.com> (raw)
In-Reply-To: <1302763208.5528.36.camel@localhost.localdomain>

On Thu, Apr 14, 2011 at 07:40:08AM +0100, Ian Campbell wrote:
> This issue is fixed in the 2.6.32-31 package currently in Debian stable.
 
I installed a DomU guest with Debian and the suggested kernel and live
migrations work properly. Thanks for all the help!

      reply	other threads:[~2011-04-14 20:44 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
2011-04-14 20:44         ` Tim M [this message]

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=20110414204448.GD6445@lumida.com \
    --to=bugs@linuxrehab.com \
    --cc=Ian.Campbell@citrix.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).