[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [xen-unstable test] 15452: regressions - FAIL
On Sat, 2013-02-09 at 07:00 +0000, xen.org wrote: > flight 15452 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/15452/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-i386-xl-credit2 14 guest-localmigrate/x10 fail REGR. vs. > 15442 > test-amd64-i386-xl-multivcpu 14 guest-localmigrate/x10 fail REGR. vs. > 15442 > test-amd64-amd64-pv 14 guest-localmigrate/x10 fail REGR. vs. > 15442 > test-amd64-i386-qemuu-rhel6hvm-intel 11 leak-check/check fail REGR. vs. > 15442 > test-amd64-i386-win 11 guest-localmigrate.2 fail REGR. vs. > 15442 > test-amd64-i386-xend-qemut-winxpsp3 11 guest-localmigrate.2 fail REGR. vs. > 15442 > test-amd64-i386-xl-qemut-win-vcpus1 7 windows-install fail REGR. vs. > 15442 > test-amd64-i386-qemut-win 11 guest-localmigrate.2 fail REGR. vs. > 15442 > test-amd64-amd64-qemut-win 7 windows-install fail REGR. vs. > 15442 > test-amd64-i386-win-vcpus1 7 windows-install fail REGR. vs. > 15442 > test-amd64-amd64-win 7 windows-install fail REGR. vs. > 15442 Of the windows install failures the xl one failed with: libxl: error: libxl.c:2101:device_disk_add: failed to get blktap devpath for 0x82ba7b0 libxl: error: libxl_create.c:901:domcreate_launch_dm: unable to add disk devices libxl: error: libxl_dm.c:1229:libxl__destroy_device_model: could not find device-model's pid for dom 2 libxl: error: libxl.c:1414:libxl__destroy_domid: libxl__destroy_device_model failed for 2 Parsing config from /etc/xen/win.guest.osstest.cfg The xend ones failed in every case with: [2013-02-09 00:11:38 2336] DEBUG (XendDomainInfo:2499) XendDomainInfo.constructDomain [2013-02-09 00:11:38 2336] ERROR (XendDomainInfo:488) VM start failed Traceback (most recent call last): File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomainInfo.py", line 473, in start XendTask.log_progress(0, 30, self._constructDomain) File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomainInfo.py", line 2576, in _constructDomain self._recreateDom() File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomainInfo.py", line 1730, in _recreateDom complete(self.dompath, lambda t: self._recreateDomFunc(t)) File "/usr/local/lib/python2.6/dist-packages/xen/xend/xenstore/xstransact.py", line 364, in complete if t.commit(): File "/usr/local/lib/python2.6/dist-packages/xen/xend/xenstore/xstransact.py", line 41, in commit rc = xshandle().transaction_end(self.transaction, False) Error: (2, 'No such file or directory') oxenstored was in use in every case, which does tend to focus the attention on: 26521:2c0fd406f02c tools/ocaml: oxenstored: Be more paranoid about ring reading 26522:ffd30e7388ad oxenstored: Enforce a maximum message size of 4096 bytes The other two changes in the range under test are x86: debugging code for testing 16Tb support on smaller memory systems xen: enable stubdom on a per arch basis which seem far less plausible. The bisector doesn't appear to be having a go at this issue though. At least one of the xend migration failures also ends with a similar xshandle().transaction_end stack trace. I don't see anything similar in any of the xl variants, but that may be down to poor logging plus the fact that xl cases are the minority and one of them has no logs. This mostly affects Windows VMs but not exclusively. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |