From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [libvirt test] 58119: regressions - FAIL Date: Tue, 23 Jun 2015 14:38:57 +0100 Message-ID: <1435066737.28264.212.camel@citrix.com> References: <1433755348.7108.402.camel@citrix.com> <20150623111538.GH3393@perard.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150623111538.GH3393@perard.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Anthony PERARD Cc: Jim Fehlig , xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com List-Id: xen-devel@lists.xenproject.org On Tue, 2015-06-23 at 12:15 +0100, Anthony PERARD wrote: > On Mon, Jun 08, 2015 at 10:22:28AM +0100, Ian Campbell wrote: > > On Mon, 2015-06-08 at 04:37 +0000, osstest service user wrote: > > > flight 58119 libvirt real [real] > > > http://logs.test-lab.xenproject.org/osstest/logs/58119/ > > > > > > Regressions :-( > > > > > > Tests which did not succeed and are blocking, > > > including tests which could not be run: > > > > This has been failing for a while now, sorry for not brining it to your > > attention sooner. > > > libxl: debug: libxl_event.c:638:libxl__ev_xswatch_deregister: watch w=0x7f805c25b248 wpath=/local/domain/0/device-model/1/state token=3/0: deregister slotnum=3 > > libxl: error: libxl_exec.c:393:spawn_watch_event: domain 1 device model: startup timed out > > libxl: debug: libxl_event.c:652:libxl__ev_xswatch_deregister: watch w=0x7f805c25b248: deregister unregistered > > libxl: debug: libxl_event.c:652:libxl__ev_xswatch_deregister: watch w=0x7f805c25b248: deregister unregistered > > libxl: error: libxl_dm.c:1564:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3) > > libxl: error: libxl_create.c:1373:domcreate_devmodel_started: device model did not start: -3 > > Hi, > > I've tried to debug this "device model: startup time out" issue that I'm > seeing on OpenStack. What I've done is strace every single QEMU. It appear > that QEMU take more than 10s to load... Looking through http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-amd64-libvirt/ALL.html when it passes the collected var-log-libvirt-libxl-libxl-driver.log.gz seems to indicate that the device model is successfully spawned in 2-4s. The same is true of the tests run on the Cambridge instance. Now, I do think the 10s timeout is a bit aggressive, on a system doing some sort of boot storm (100s of parallel vm starts) it's not out of the question that spawning qemu might take a little while. _But_ osstest is not doing that, the single virsh create is essentially the only thing happening on the box. Ian.