Re: Enormous size of libvirt libxl-driver.log with Xen 4.2 and 4.3

[Ian Campbell <ian.campbell@citrix.com>]

On Tue, 2015-08-11 at 11:19 +0100, Ian Campbell wrote:
> On Mon, 2015-08-03 at 11:47 +0100, Ian Campbell wrote:
> > After the initial expected logging the file is simply full of:
> > 
> > 2015-08-02 19:12:12 UTC libxl: debug: 
> > libxl.c:1004:domain_death_xswatch_callback: [evg=0x7f3cc44fa3f0:3] from 
> > domid=0 nentries=1 rc=1
> > 2015-08-02 19:12:12 UTC libxl: debug: 
> > libxl.c:1015:domain_death_xswatch_callback: [evg=0x7f3cc44fa3f0:3]  
> >  got=domaininfos[0] got->domain=0
> > 2015-08-02 19:12:12 UTC libxl: debug: 
> > libxl.c:1015:domain_death_xswatch_callback: [evg=0x7f3cc44fa3f0:3]  
> >  got=domaininfos[1] got->domain=-1
> > 2015-08-02 19:12:12 UTC libxl: debug: 
> > libxl.c:1023:domain_death_xswatch_callback:  got==gotend
> > 
> > Repeated at around 51KHz.
> 
> This sounds a lot like 4783c99aab8 (see below for full log message), 
> which
> perhaps ought to be backported to the effected branches, i.e. 4.2 and 
> 4.3. 
> 
> Looks like it was backported to 4.5 (as 0b19348f3cd1) and 4.4 (as
> 13623d5d8e85) already.
> 
> Ian?

I just saw this one go past on the changelog list, so I've removed 

branches/for-qemu-upstream-4.3-testing.git/stop
branches/for-xen-4.2-testing.git/stop
branches/for-xen-4.3-testing.git/stop