>>> On 02.02.16 at 11:56, <yu.c.zh...@linux.intel.com> wrote: > I understand your concern, and to be honest, I do not think > this is an optimal solution. But I also have no better idea > in mind. :( > Another option may be: instead of opening this parameter to > the tool stack, we use a XenGT flag, which set the rangeset > limit to a default value. But like I said, this default value > may not always work on future XenGT platforms.
Assuming that you think of something set e.g. by hypervisor command line option: How would that work? I.e. how would that limit the resource use for all VMs not using XenGT? Or if you mean a flag settable in the domain config - how would you avoid a malicious admin to set this flag for all the VMs created in the controlled partition of the system? Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
