Re: [Libvir] [PATCH] finish NUMA code reorg, plug cpuset at creat time support

I tested with the latest code, and found a problem with specifying a value in the cpuset in XML that is greater than maxcpu-1. The attached patch corrects this behavior, but the issue remains that an out of range cpu will prevent the domain from starting. This is the way xm create works today.

In talking with Daniel about this, he made the point that it is not necessarily desirable for the failure of a tuning parameter (e.g., config specifies cpu 5 and the domain is now being started on a 4 cpu machine) to cause domain creation to fail. He mentioned phones ringing in the middle of the night somewhere for support when the domain fails to start. I think he has a point. Wouldn't it make more sense to start the domain(s) at perhaps suboptimal performance, than to have everything shut down until someone can come and figure out the problem? It would seem better if the domain started (with no cpu affinity) and a warning was posted. This might also argue for separation of domain config and tuning parameters. Or at least for 2 flavors of create? One that fails if tuning parameters cannot be activated, and one that doesn't.