From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Xu, Jiajun" <jiajun.xu@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Jim Fehlig <jfehlig@novell.com>
Subject: Re: Biweekly VMX status report. Xen: #21237 & Xen0: #a3e7c7...
Date: Mon, 10 May 2010 13:40:47 +0100 [thread overview]
Message-ID: <C80DBD5F.13CEB%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A1E6E839E@shsmsx501.ccr.corp.intel.com>
Thanks I will apply the patch to xen-unstable and xen-4.0 and leave 21223 in
place (not reverted).
K.
On 10/05/2010 13:34, "Xu, Jiajun" <jiajun.xu@intel.com> wrote:
> Hi Keir,
> I tried the patch. It can fix the SR/LM issue.
>
>> -----Original Message-----
>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
>> Sent: Sunday, May 09, 2010 10:59 PM
>> To: Xu, Jiajun; xen-devel@lists.xensource.com
>> Cc: Jim Fehlig
>> Subject: Re: [Xen-devel] Biweekly VMX status report. Xen: #21237 & Xen0:
>> #a3e7c7...
>>
>> On 09/05/2010 15:21, "Xu, Jiajun" <jiajun.xu@intel.com> wrote:
>>
>>> New Bugs (4):
>>>
>> ================================================================
>> ====
>>> 1. Save/Restore and Live Migration can not work
>>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1609
>>
>> Could xen-unstable:21223 be to blame? Can you reproduce this bug if you
>> revert that changeset? How about with the attached patch added (and with
>> 21223 not reverted) -- I think this patch is intended as a fix for 21223.
>>
>> Thanks,
>> Keir
>
prev parent reply other threads:[~2010-05-10 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-09 14:21 Biweekly VMX status report. Xen: #21237 & Xen0: #a3e7c7 Xu, Jiajun
2010-05-09 14:59 ` Keir Fraser
2010-05-10 12:34 ` Xu, Jiajun
2010-05-10 12:40 ` Keir Fraser [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=C80DBD5F.13CEB%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=jfehlig@novell.com \
--cc=jiajun.xu@intel.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).