Re: [Xen-devel] [linux-linus test] 17480: regressions - FAIL

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [linux-linus test] 17480: 
regressions - FAIL"):
> It is the same as the last one - the install of RHEL6 fails
> and the migrate of a guest fails.
...
> What would be useful is to figure out what 'mite' thought about the
> migration, but sadly the 'val/log/xen/xend.log' file shows nothing!?
> http://www.chiark.greenend.org.uk/~xensrcts/logs/17480/test-amd64-i386-pair/gall-mite---var-log-xen-xend.log

http://www.chiark.greenend.org.uk/~xensrcts/logs/17480/test-amd64-i386-pair/itch-mite---var-log-xen-xend.log

shows various messages from itch-mite's xc_restore.  It seems to be
receiving pages up to about 12:50:54 and then everything goes quiet.
During the log capture, we can see xc_restore still running.

> Anyhow, the failure is with xc_save which tells us this command:
> 
> xm migrate debian.guest.osstest itch-mite
> 
> fails with:
> + exit 4

The failure happens before then, here:

2013-04-05 11:57:04 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_17480.test-amd64-i386-pair
root@xxxxxxxxxxxxx xm migrate debian.guest.osstest itch-mite

Ie, the test system waited 400s and then gave up.

The stuff about exit status 4 is a shell wrapper for the test script,
to record the test script exit status.  It doesn't mean that xc_save
exited with status 4.

I think xc_save was probably killed when the tester killed the ssh
connection which was running xm migrate.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel