Testcase for HVM vNUMA

Hi,

This small series implements an HVM vNUMA test case.

It is all as simple as adding (and handling) a runvar, holding the number of vNUMA nodes we want, to the regular debian HVM test case.

For now, the resulting topology used in the test is hardcoded. This means that, as soon as the number of vNUMA nodes we want is known (via the said runvar), the rest of the configuration (how much memory in each vnode, which vcpus, etc) is derived automatically, by splitting as evenly as we can the guest resources.

Note that we do not yet support save/restore and migration for vNUMA enabled guests, so this test will fail (and in fact, it's added to the non-blocking list). Since I think we should, at some point, support both, things are ok to be that way.

I've tested in standalone mode, and it appear to me to be working properly (or, I should say, "to not be working, as expected" :-D).

I'll reply to this very email with the diff of the runvars before and after the series as soon as standalone-generate-dump-flight-runvars will finish running. :-)

Regards,
Dario
---

Dario Faggioli (2):
TestSupport.pm: allow creating vNUMA enabled HVM guest configs
make-flight: create the vNUMA HVM test job

 Osstest/TestSupport.pm |   29 +++++++++++++++++++++++++++++
 allow.all              |    1 +
 make-flight            |   36 ++++++++++++++++++++++++++++++++++--
 3 files changed, 64 insertions(+), 2 deletions(-)

--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)