Re: [Xen-devel] [libvirt test] 58119: regressions - FAIL

[Anthony PERARD <anthony.perard@xxxxxxxxxx>]

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 :-(
> 
> This has been failing for a while now, sorry for not brining it to your
> attention sooner.
> 
> amd64 and arm look like:
> 
> 2015-06-08 02:25:15 Z executing ssh ... root@xxxxxxxxxxxxx virsh create 
> --file /etc/xen/debian.guest.osstest.cfg.xml
> error: Failed to create domain from /etc/xen/debian.guest.osstest.cfg.xml
> error: internal error: libxenlight failed to create new domain 
> 'debian.guest.osstest'
> 
> and from the driver log:
> 
> 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
> 
> i386 is:
> 
> 2015-06-07 21:45:32 Z executing ssh ... root@xxxxxxxxxxxxx virsh create 
> --file /etc/xen/debian.guest.osstest.cfg.xml
> 2015-06-07 21:46:12.853+0000: 16327: info : libvirt version: 1.2.17
> 2015-06-07 21:46:12.853+0000: 16327: warning : virKeepAliveTimerInternal:143 
> : No response from client 0xb6fe7c38 after 6 keepalive messages in 35 seconds
> 2015-06-07 21:46:12.854+0000: 16326: warning : virKeepAliveTimerInternal:143 
> : No response from client 0xb6fe7c38 after 6 keepalive messages in 35 seconds

The "No response from client ..." appear only on armhf as far as I can
tell.

> error: Failed to create domain from /etc/xen/debian.guest.osstest.cfg.xml
> error: internal error: received hangup / error event on socket
> 
> libvirtd is still there in the ps log.
> 
> Histories:
> 
> http://logs.test-lab.xenproject.org/osstest/results/history.test-amd64-amd64-libvirt.libvirt.html
> http://logs.test-lab.xenproject.org/osstest/results/history.test-amd64-i386-libvirt.libvirt.html
> http://logs.test-lab.xenproject.org/osstest/results/history.test-armhf-armhf-libvirt.libvirt.html

What is different about merlot[01] hosts? When looking at a more general
view of test-amd64-amd64-libvirt, the test always fail on merlot[01], but
it is likely to pass on other host:

http://logs.test-lab.xenproject.org/osstest/results/history.test-amd64-amd64-libvirt
http://logs.test-lab.xenproject.org/osstest/results/history.test-amd64-i386-libvirt

-- 
Anthony PERARD

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