Comment 8 for bug 1621121

On Tue, Oct 25, 2016 at 6:04 AM, Robert Williams <email address hidden> wrote:

> Appreciate this is due to be looked at in 17.04 - but - is there a
> workaround for manually linking numad so that libvirt finds it? From
> what i can see, it's been built with the library, so, providing numad is
> operational it should be a case of showing libvirt where it is. Unless
> i'm missing something?
>
> I have several hosts where numad is installed and operational so if i
> knew where libvirt was looking for numad then maybe it can be linked in
> to get it working under 16.04 LTS?
>

I don't think this is possible; the feature is a build-time feature and we
cannot
enable it as it requires including numad which is part of Universe for a
package
in main.

As a workaround, you could rebuild the package with the added config flag
in a PPA.

I'll see if I can get such a build into my own PPA and share the debdiff
here.

numad itself will need a MIR[1] and be approved before it can be part of
main.

1. https://wiki.ubuntu.com/MainInclusionProcess

> Thanks in advance,
>
> --
> You received this bug notification because you are a member of Ubuntu
> Virtualisation 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/16211
> 21/+subscriptions
>