From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Is: events not being cleared during fast migration over InfiniBand Was: Re: xen 4.3 test report
Date: Thu, 13 Jun 2013 09:14:28 -0400 [thread overview]
Message-ID: <20130613131427.GD6303@konrad-lan.dumpdata.com> (raw)
In-Reply-To: <CACaajQuSRa9Yy9QGn=VVzeVucwi5aBEVTtXpqurKYhatdWhF4g@mail.gmail.com>
On Thu, Jun 13, 2013 at 03:22:17PM +0400, Vasiliy Tolstov wrote:
> Any news about this bug? I don't understand why in case of using
> xend/xm bug not appeared.
> I think that xl and xm use identical sequence and identical operations
> when migrate domain...
Hey Vasiliy,
I've been busy with another bug in the Xen code and am wrapping it up
now.
next prev parent reply other threads:[~2013-06-13 13:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 10:40 xen 4.3 test report Vasiliy Tolstov
2013-05-24 12:46 ` George Dunlap
2013-05-24 13:15 ` Vasiliy Tolstov
2013-05-24 14:11 ` Konrad Rzeszutek Wilk
2013-05-24 14:38 ` George Dunlap
2013-05-24 20:15 ` Vasiliy Tolstov
2013-05-25 11:40 ` Konrad Rzeszutek Wilk
2013-05-27 5:32 ` Vasiliy Tolstov
2013-05-28 15:31 ` Konrad Rzeszutek Wilk
2013-05-28 20:58 ` Vasiliy Tolstov
2013-05-31 4:56 ` Vasiliy Tolstov
2013-06-03 14:08 ` Konrad Rzeszutek Wilk
2013-06-04 12:17 ` Vasiliy Tolstov
2013-06-05 18:50 ` Is: events not being cleared during fast migration over InfiniBand Was: " Konrad Rzeszutek Wilk
2013-06-06 9:23 ` George Dunlap
2013-06-06 9:25 ` George Dunlap
2013-06-13 11:22 ` Vasiliy Tolstov
2013-06-13 13:14 ` Konrad Rzeszutek Wilk [this message]
2013-06-13 13:17 ` Vasiliy Tolstov
2013-06-13 11:24 ` Vasiliy Tolstov
2013-05-25 11:27 ` Konrad Rzeszutek Wilk
2013-05-24 20:13 ` Vasiliy Tolstov
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=20130613131427.GD6303@konrad-lan.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=v.tolstov@selfip.ru \
--cc=xen-devel@lists.xen.org \
/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.