xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: xen 4.3 test report
Date: Mon, 3 Jun 2013 10:08:37 -0400	[thread overview]
Message-ID: <20130603140837.GP6893@phenom.dumpdata.com> (raw)
In-Reply-To: <CACaajQvAxOCCc-=sGm_ZCf+Z8w__o2f3+wD9obRKZjOK98kQfw@mail.gmail.com>

On Fri, May 31, 2013 at 08:56:47AM +0400, Vasiliy Tolstov wrote:
> migration with qemu-xen-traditional:
> xen16:~ # xl migrate --debug 21-10887 ib-xen06.kh11.clodo.ru
> the global config option vifscript is deprecated, please switch to
> vif.default.script
> the global config option vifscript is deprecated, please switch to
> vif.default.script
> migration target: Ready to receive domain.
> Saving to migration stream new xl format (info 0x0/0x0/631)
> Loading new save file <incoming migration stream> (new xl fmt info 0x0/0x0/631)
>  Savefile contains xl domain config
> xc: progress: Reloading memory pages: 53248/1048576    5%
> xc: progress: Reloading memory pages: 105472/1048576   10%
> xc: progress: Reloading memory pages: 157658/1048576   15%
> xc: progress: Reloading memory pages: 209882/1048576   20%
> xc: progress: Reloading memory pages: 263130/1048576   25%
> migration receiver stream contained unexpected data instead of ready message
> (command run was: exec ssh ib-xen06.kh11.clodo.ru xl migrate-receive -d )
> migration target: Transfer complete, requesting permission to start domain.
> libxl: error: libxl_utils.c:393:libxl_read_exactly: file/stream
> truncated reading GO message from migration stream
> migration target: Failure, destroying our copy.
> migration child [15697] not exiting, no longer waiting (exit status
> will be unreported)
> Migration failed, resuming at sender.
> migration target: Cleanup OK, granting sender permission to resume.
> 
> xl dmesg:
> (XEN) event_channel.c:297:d1 d1v0 [evtchn_bind_virq:297], port:3, rc:-17
> (XEN) event_channel.c:298:d1 EVTCHNOP failure: error -17

The non-debug version tells me it is:

289     if ( (port = get_free_port(d)) < 0 )                                        
290         ERROR_EXIT(port);            

Which gets -EEXIST from get_free_port. But get_free_port only returns
-EINVAL, -ENOMEM, and -ENOSPC in failure modes.

But we get -EEXIST? Could you re-run git diff and attach output to
this email? I think you tweaked the debug code a bit so I am looking
at something different?

  reply	other threads:[~2013-06-03 14:08 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 [this message]
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=20130603140837.GP6893@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Jackson@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 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).