Comment 3 for bug 1621121

The failure is about numad (vs. libnuma).

I think what's needed here is libvirt to be built with
 '--with-numa=/path/to/numad' (which it isn't).

However, numad is part of universe and libvirt can't depend upon a package
in universe since it's part of main IIUC.

On Fri, Sep 9, 2016 at 12:57 AM, ChristianEhrhardt <
<email address hidden>> wrote:

> Hi,
> libvirt is build --with-numactl on
> amd64 i386 ia64 mips mipsel powerpc ppc64el s390x
>
> You can check effectively if it was built against it by checking for the
> lib depend like:
> ldd /usr/sbin/libvirtd | grep numa
> libnuma.so.1 => /usr/lib/x86_64-linux-gnu/libnuma.so.1
> (0x00007f99e4a39000)
>
> For further debugging until we can reproduce, can you enable more
> debugging of libvirt and add the more verbose libvirt log here so you and
> we can check for issues in it?
> See:
> http://libvirt.org/guide/html/Application_Development_Guide-
> Connections-Debug.html
>
> --
> You received this bug notification because you are a member of Ubuntu
> Xen Team, which is subscribed to libvirt in Ubuntu.
> https://bugs.launchpad.net/bugs/1621121
>
> Title:
> VM fails to start when vcpu placement='auto'
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/
> 1621121/+subscriptions
>