From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: George Dunlap <dunlapg@umich.edu>, Ian.Jackson@eu.citrix.com
Cc: Vasiliy Tolstov <v.tolstov@selfip.ru>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xen 4.3 test report
Date: Fri, 24 May 2013 10:11:50 -0400 [thread overview]
Message-ID: <20130524141150.GA3900@phenom.dumpdata.com> (raw)
In-Reply-To: <CAFLBxZYxOyVZm+G-SU8EZdi4yi+eA6RN4-nZuo8DxDPyhiE-=Q@mail.gmail.com>
On Fri, May 24, 2013 at 01:46:11PM +0100, George Dunlap wrote:
> On Fri, May 24, 2013 at 11:40 AM, Vasiliy Tolstov <v.tolstov@selfip.ru> wrote:
> > Hello. I'm try 4.3.0-rc2 and have very very small speed of live
> > migration (is about 2 hours for 1Gb memory) but if i start xend and
> > doing xm migrate domain successeful migrated to destionation and this
> > takes is about 3-6 seconds (i'm use infiniband)
> >
> > Why this happening?
>
> Hmm -- I think this has been mentioned a couple of times, but I don't
> think anyone has looked into it. I'll see if I can track it down.
I've noticed on Xen 4.1 (and Xen 4.3) that if I use a 32-bit dom0 and
local migrated any 32/64 PV/PVHVM (so four variations) guest it is incredibly slow.
(So xm save <..> in an iSCSI disk && xm restore ...)
The 'perf report' shows that dom0 spends most of its time in xen_version
(which is the yield type call).
If the same operation is done, but dom0 is a 64-bit, it is quick.
And I think this is the issue that Ian's Jackson nighlty test-system is
running in-to - which is that the migration is sooo slow that it times out.
(This is with real-linux).
Now the oddity is that this I saw this with Xen 4.1, but Vasiliy says he didn't see
this with Xen 4.1 - so perhaps the issue I am seeing is different.
Hm, I should re-run this test once more with xen 4.3 just to confirm.
>
> >
> > And second question - why i can't migrate from 4.1.3 (xend) to
> > 4.3.0-rc2 (xend) ?
>
> I think migration is only supported for one major release -- does it
> work from 4.1 to 4.2, then 4.2 to 4.3?
>
> -George
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-05-24 14:11 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 [this message]
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
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=20130524141150.GA3900@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dunlapg@umich.edu \
--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 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).