On Sat, 2006年12月09日 at 13:47 +0000, Keir Fraser wrote:
> Done. You shouldn't need HVM_PARAM_VCPUS: the tools have already
> setmaxvcpus, and this number is available to your HVM builder by doing a
> getdomaininfo and using max_vcpu_id (plus one). HVM params are really
> intended for registering values that Xen has some interest in -- which is
> not the case for this particular parameter (since it's redundant).
Hi Keir,
Thanks for the advice, I fixed this to use getdomaininfo in our
current tree. We also have two other tiny fixes in the tree that would
be nice to get in for 3.0.4. Please pull the xen-ia64-unstable tree to
pick these up:
http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel