Comment 10 for bug 1621121

Hi,
I wanted to at least confirm the suggestion of Ryan.

In the configure of libvirt source this is:
   --with-numad use numad to manage CPU placement dynamically
                           [default=check]

I built it with numad as build time dependency to see if it picks all up correctly.
It does, it ends up with:
  configure: numad: yes

As for the binary dependency I would only choose a "suggests".
Because to quote numad's NEWS file:
  Starting or stopping the 'numad' daemon while running a large virtual
  machine may be dangerous so installing (or removing) this package won't
  start (or stop) it.

Due to its nature numad can cause severe overhead as well as impact an existing system when moving or constraining numa attributed of processes.

So I was a bit afraid it could add a binary dependency via shlibs or so.
But it seems to be ok knowing numad exists - and since it is no lib but only a binary it does not add a dep.

Here in my newly built Deb dir:
for i in $(ls -1 *.deb | sed 's/.deb//'); do apt-cache show $i | grep numad; done
Suggests: libvirt-daemon-system, numad

The diff to get there is trivial, I'll attach it.
But as Ryan suggested the thing needed is a MIR for numad.