WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [xen-unstable test] 2089: regressions - FAIL

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [xen-unstable test] 2089: regressions - FAIL
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Tue, 7 Sep 2010 15:36:50 +0100
Delivery-date: Tue, 07 Sep 2010 07:37:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <E1OspnX-0003za-Ga@xxxxxxxxxxxxxxxxxxx>
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: <E1OspnX-0003za-Ga@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Ian Jackson writes ("[xen-unstable test] 2089: regressions - FAIL"):
> test-amd64-amd64-win          4 xen-boot                fail REGR. vs. 2063

These seem to be something to do with blktap.  (NB that this is
different from the Linux ballooning problem Jeremy is investigating.)

Looking back at past test results it appears that there is an
intermittent problem starting xend.  The symptoms are that the xend
startup script never returns, and thus the dom0 bootup does not
complete.  I think it must be a race.

For example, looking at this failure:
 
http://www.chiark.greenend.org.uk/~xensrcts/logs/2089/test-amd64-amd64-win/info.html

The serial log shows:

Sep  6 21:43:15.283632 ^M
Sep  6 21:43:15.283647 Setting domain 0 name...^M
Sep  6 21:43:15.283666 Starting xenconsoled...^M
Sep  6 21:43:15.288631 Sep  6 21:44:05.088381 <Modem lines changed: -CTS -DSR>

(where the event at 21:44 is the test system starting to power cycle
the host to wipe it for the next test)

The xend log stops after:

[2010-09-06 21:43:17 3659] DEBUG (XendDomain:410) number of vcpus to use is 0

and a ps listing shows this:

 3270 ? Ss 00:00:00 0 1 0.0 0.3  7d495 wait      /bin/sh /etc/init.d/rc 2
 3638 ? S  00:00:00 0 0 0.0 0.2  7d495 wait       \_ /bin/bash 
/etc/rc2.d/S93xend start
 3642 ? S  00:00:00 0 0 0.6 2.4 123e67 pipe_wait      \_ /usr/bin/python 
/usr/sbin/xend start
 3656 ? Z  00:00:00 0 0 0.0 0.0  7de50 exit               \_ [blktapctrl] 
<defunct>
 3657 ? Zs 00:00:00 0 1 0.0 0.0  7de50 exit               \_ [xend] <defunct>


Compare this to a successful run:
 
http://www.chiark.greenend.org.uk/~xensrcts/logs/2089/test-amd64-amd64-pair/info.html
(look at the entries for src_host rather than dst_host).

The xend.log continues with:

[2010-09-07 04:11:35 3283] DEBUG (XendDomainInfo:1881) 
XendDomainInfo.handleShutdownWatch
[2010-09-07 04:11:35 3283] WARNING (XendAPI:708) API call: VBD.set_device not 
found

and the ps listing of the successful bootup shows:

 3281 ? S   00:00:00 0 0 0.0 1.9  7d495 wait                  /usr/bin/python 
/usr/sbin/xend start
 3283 ? SLl 00:00:01 0 0 1.4 2.8 ffffff poll_schedule_timeout  \_ 
/usr/bin/python /usr/sbin/xend start


Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>