From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Fehlig Subject: Re: [xen-unstable test] 35257: regressions - FAIL Date: Mon, 02 Mar 2015 10:59:50 -0700 Message-ID: <54F4A516.3020201@suse.com> References: <1425030149.14641.119.camel@citrix.com> <20150227104829.GA29195@zion.uk.xensource.com> <1425042785.14641.188.camel@citrix.com> <54F0D7FE.4080203@suse.com> <21748.17914.317136.91748@mariner.uk.xensource.com> <1425296288.1886.37.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1425296288.1886.37.camel@citrix.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: Ian Campbell Cc: Wei Liu , xen-devel@lists.xensource.com, Ian Jackson List-Id: xen-devel@lists.xenproject.org Ian Campbell wrote: > On Mon, 2015-03-02 at 11:14 +0000, Ian Jackson wrote: > >> Jim Fehlig writes ("Re: [Xen-devel] [xen-unstable test] 35257: regressions - FAIL"): >> ... >> >>> In my experience, if ERROR is insufficient, INFO and WARNING don't >>> help. DEBUG is needed. >>> >> Where does virtd's stderr go ? That is where any assertion failure >> message would be written. >> > > /dev/null from the looks of the code: > http://libvirt.org/git/?p=libvirt.git;a=blob;f=daemon/libvirtd.c;h=2366d63cd3c70f75df5af82d2c241df163293eab;hb=HEAD#l174 > When daemonized, yes :-/. You would need to run libvirtd without the '-d' option to see the assert. Or collect a core as Ian suggested. Regards, Jim