From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: "xen.org" <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [linux-linus test] 17458: regressions - FAIL
Date: Sun, 31 Mar 2013 15:55:31 -0400 [thread overview]
Message-ID: <20130331195531.GA19156@konrad-lan.dumpdata.com> (raw)
In-Reply-To: <osstest-17458-mainreport@xen.org>
On Sun, Mar 31, 2013 at 03:26:14PM +0100, xen.org wrote:
> flight 17458 linux-linus real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/17458/
>
> Regressions :-(
So that is migrate failing with rc 4 and it is still stuck at
gall:
2013-03-31 10:57:27 Z command timed out [400]: ssh -o
StrictHostKeyChecking=no -o BatchMode=yes -o ConnectTimeout=100 -o
ServerAliveInterval=100 -o PasswordAuthentication=no -o
ChallengeResponseAuthentication=no -o
UserKnownHostsFile=tmp/t.known_hosts_17458.test-amd64-i386-pair
root@10.80.249.149 xm migrate debian.guest.osstest itch-mite
status (timed out) at Osstest/TestSupport.pm line 375.
+ rc=4
+ date -u '+%Y-%m-%d %H:%M:%S Z exit status 4'
2013-03-31 10:57:28 Z exit status 4
+ exit 4
Error: /usr/lib/xen/bin/xc_save 23 1 0 0 0 failed
Usage: xm migrate <Domain> <Host>
I am not having much luck finding what the rc 4 is actually.
The guest thinks the migrate went OK:
debian login: [ 31.589140] PM: freeze of devices complete after 0.434
msecs
[ 31.589311] PM: late freeze of devices complete after 0.137 msecs
[ 31.589494] PM: noirq freeze of devices complete after 0.164 msecs
[ 31.590065] Grant tables using version 2 layout.
[ 31.590065] PM: noirq thaw of devices complete after 0.027 msecs
As in, it did it (the freeze part), and then restored again (thaw).
prev parent reply other threads:[~2013-03-31 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 14:26 [linux-linus test] 17458: regressions - FAIL xen.org
2013-03-31 19:55 ` Konrad Rzeszutek Wilk [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=20130331195531.GA19156@konrad-lan.dumpdata.com \
--to=konrad@kernel.org \
--cc=ian.jackson@eu.citrix.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 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.