This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [xen-4.0-testing test] 2045: regressions - FAIL

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] [xen-4.0-testing test] 2045: regressions - FAIL
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Wed, 25 Aug 2010 19:25:19 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 25 Aug 2010 11:26:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100825154011.GO2804@xxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <E1OoGrO-0004eo-E3@xxxxxxxxxxxxxxxxxxx> <20100825154011.GO2804@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Pasi Kärkkäinen writes ("Re: [Xen-devel] [xen-4.0-testing test] 2045: 
regressions - FAIL"):
> So ok, half of these failures are xl related..
> How about the other failures?

These failures are as follows:

test-amd64-i386-pair    12 guest-migrate/src_host/dst_host fail REGR. vs. 1993

It seems that PV migration of a domain from one host to another
doesn't work properly.  Looking at the logs everything is absolutely
fine except that the domU isn't responding to arps and pings for at
least the 20s that the test system waits 20s after migration.

test-amd64-i386-win           5 windows-install            fail REGR. vs. 1993
test-i386-i386-win            5 windows-install            fail REGR. vs. 1993

These were HVM installs of Windows.  The timed out after 7000s.
Looking at the logs, the test harness tried to collect various
information including screenshots, but this generally failed because
the dom0 was running very very slowly.  For example,
  ssh root@<dom0> brctl show
took 7 secons to run; and
  ssh root@<dom0> xenstore-read <some thing to find VNC port>
took more than 10 seconds which made the test harness time it out.

I have seen these symptoms myself: dom0 can become very unresponsive
indeed, sometimes locking up (or at least, not listening to the
network) for tens of seconds at a time.

test-amd64-amd64-xl          10 guest-stop                   fail   never pass
test-amd64-i386-xl           10 guest-stop                   fail   never pass
test-amd64-xcpkern-i386-xl   10 guest-stop                   fail   never pass
test-i386-i386-xl            10 guest-stop                   fail   never pass
test-i386-xcpkern-i386-xl    10 guest-stop                   fail   never pass

This is because "xl shutdown -w" is not implemented.

test-i386-xcpkern-i386-pair  12 guest-migrate/src_host/dst_host fail like 1993
test-i386-i386-pair         12 guest-migrate/src_host/dst_host fail never pass

I haven't looked into these.

test-amd64-amd64-pair           <none executed>              fail

This is a malfunction in the test infrastructure.


Xen-devel mailing list