From: Keir Fraser <keir.xen@gmail.com>
To: MaoXiaoyun <tinnycloud@hotmail.com>,
xen devel <xen-devel@lists.xensource.com>
Subject: Re: Xen live migration
Date: Tue, 19 Apr 2011 14:20:07 +0100 [thread overview]
Message-ID: <C9D34A97.169AA%keir.xen@gmail.com> (raw)
In-Reply-To: <BLU157-w53E546D905E7F3979E5CF2DA900@phx.gbl>
On 19/04/2011 14:05, "MaoXiaoyun" <tinnycloud@hotmail.com> wrote:
> Hi:
>
> I've been noticed that intel XSAVE is disabled in Xen source.
> Does this mean live migration is temporarily not support right now?
> Is it for buggy reason, will be enable again someday later?
XSAVE doesn't have anything to do with live migration.
-- Keir
> thanks.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-04-19 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 13:05 Xen live migration MaoXiaoyun
2011-04-19 13:20 ` Keir Fraser [this message]
2011-04-20 9:21 ` Tim Deegan
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=C9D34A97.169AA%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=tinnycloud@hotmail.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).