Re: [libvirt test] 55257: regressions - FAIL

[Anthony PERARD <anthony.perard@citrix.com>]

On Wed, May 13, 2015 at 09:46:28AM +0100, Ian Campbell wrote:
> On Mon, 2015-05-11 at 10:36 -0600, Jim Fehlig wrote:
> [...]
> > > The qemu log is sadly empty so I've no clue why this timed out.
> > >   
> > 
> > I guess qemu didn't run at all...
> > 
> > > Perhaps there is something in 
> > > http://logs.test-lab.xenproject.org/osstest/logs/55257/test-amd64-amd64-libvirt/merlot1---var-log-libvirt-libvirtd.log.gz
> > > I can't make heads nor tail though.
> > >   
> > 
> > Nothing interesting.  Only the unhelpful
> > 
> > 2015-05-11 12:42:17.451+0000: 4280: error : libxlDomainStart:1032 :
> > internal error: libxenlight failed to create new domain
> > 'debian.guest.osstest'
> 
> This happened again in
> http://logs.test-lab.xenproject.org/osstest/logs/55349/test-amd64-amd64-libvirt/info.html
> 
> Is there anything we could tweak in osstest to produce more helpful
> logging?

Well we can find in var-log-libvirt-libvirtd.log.gz this:
2015-05-12 17:39:35.180+0000: 4329: error : libxlDomainStart:1032 : internal error: libxenlight failed to create new domain 'debian.guest.osstest'

And for more information we need to look into the driver specific log,
libxl logs in var-log-libvirt-libxl-libxl-driver.log:
libxl: error: libxl_exec.c:393:spawn_watch_event: domain 1 device model: startup timed out

I'm seeing this error a lot on our OpenStack CI loop, I thought the error
was due to the "host" been very busy, but if osstest is having the same
issue, then there is probably something wrong with libxl+libvirt :(.

-- 
Anthony PERARD