[libvirt] [Xen-devel] [xen-unstable test] 35257: regressions - FAIL

[Jim Fehlig]

Ian Campbell wrote:
> On Thu, 2015-02-26 at 20:14 +0000, xen.org wrote:
>   
>> flight 35257 xen-unstable real [real]
>> http://www.chiark.greenend.org.uk/~xensrcts/logs/35257/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>>  test-armhf-armhf-libvirt     12 guest-start.2             fail REGR. vs. 34629
>>     
>
> logs:
> http://www.chiark.greenend.org.uk/~xensrcts/logs/35257/test-armhf-armhf-libvirt/info.html
>
> http://www.chiark.greenend.org.uk/~xensrcts/logs/35257/test-armhf-armhf-libvirt/12.ts-guest-start.log
>         2015-02-23 20:21:48 Z executing ssh ... root at 10.80.229.106 virsh domxml-from-native xen-xl /etc/xen/debian.guest.osstest.cfg > /etc/xen/debian.guest.osstest.cfg.xml
>         error: failed to connect to the hypervisor
>         error: no valid connection
>         error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused
>
> http://www.chiark.greenend.org.uk/~xensrcts/logs/35257/test-armhf-armhf-libvirt/marilith-n4-output-ps_wwwaxf_-eo_pid%2Ctty%2Cstat%2Ctime%2Cnice%2Cpsr%2Cpcpu%2Cpmem%2Cnwchan%2Cwchan%2325%2Cargs
> appears to show no libvirtd process.
>
> http://www.chiark.greenend.org.uk/~xensrcts/logs/35257/test-armhf-armhf-libvirt/marilith-n4---var-log-libvirt-libvirtd.log
> says:
>         2015-02-23 20:13:15.556+0000: 2133: info : libvirt version: 1.2.13
>         2015-02-23 20:13:15.556+0000: 2133: error : dnsmasqCapsRefreshInternal:726 : Cannot check dnsmasq binary dnsmasq: No such file or directory
>   
> 2015-02-23 20:13:15.845+0000: 2133: error :
> virFirewallValidateBackend:193 : direct firewall backend requested,
> but /sbin/ebtables is not available: No such file or directory

Odd, since ebtables was found when building

checking for ebtables... /sbin/ebtables

But AFAICT, that wont prevent libvirtd from starting.

>         
> I think these are just spurious.
>
>         2015-02-23 20:13:15.845+0000: 2133: error : virFirewallApply:936 : out of memory
>         
>
>         2015-02-23 20:13:16.092+0000: 2133: error : virExec:491 : Cannot find 'pm-is-supported' in path: No such file or directory
>         2015-02-23 20:13:16.092+0000: 2133: warning : virQEMUCapsInit:999 : Failed to get host power management capabilities
>         
> As are these two.
>         
>         2015-02-23 20:13:16.400+0000: 2133: error : virFirewallApply:936 : out of memory
>
> Has these OOM messages resulted in libvirtd exiting?

No, I don't think so.  The related code is

int
virFirewallApply(virFirewallPtr firewall)
{
    size_t i, j;
    int ret = -1;

    virMutexLock(&ruleLock);

    if (!firewall || firewall->err == ENOMEM) {
        virReportOOMError();
        goto cleanup;
    ...
}

I suspect 'firewall' is null, so OOM error is reported and the function
returns -1.  But I also don't see this preventing libvirtd from
starting.  I've cc'd the libvirt list for verification that these errors
won't prevent libvirtd from starting.

>  I don't see any
> evidence of a crash elsewhere in the logs (i.e. no "process segfaulted"
> in dmesg, no OOM killing going on etc).
>
> We don't seem to collect dom0 freemem info, but that most likely
> wouldn't help given the libvirtd process has exited.
>
>   
> Any ideas where to look next?

Can you access the test environment and try starting libvirtd in the
foreground?  Or enable debug log level in /etc/libvirt/libvirtd.conf?

Regards,
Jim