I am not a user, so my feelings here may be incorrect, but it seems it might be unpleasant to have to modify 30 (for example) domain configs when I'm trying to rework tuning information for a machine. I could imagine a single config file that contains cpu_weight, cpu_cap, the cpuset, and whatever other tuning information per domain might be appropriate. Looking at a single file to tweak such values across multiple domains might be preferable, and make the situation easier to visualize. Jim Fehlig wrote:
David Lutterkort wrote:
On Fri, 2007-10-26 at 09:08 -0400, Daniel Veillard wrote:
I can understand the need to make it easy for an user, I still don't think this means those tuning informations need to be associated to the domain definition, to me it is somehow orthogonal to the domain themselves and I would rather try to provide a good solution to the problem, than try to imitate how Xen was doing that.
Surely, users who set tuning parameters view them as part of their domain description.
I agree. It appears the discussions around recent Linux-VServer patches includes tuning information in the XML description so I'm a little confused if this idea is being received positively or not.
I would like to avoid calling out to some other API for scheduling parameters at domU definition if at all possible. Perhaps I've been away too long and this functionality already exists :-), but not seeing it in http://www.libvirt.org/format.html
Regards, Jim
-- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
-- Elizabeth Kon (Beth) IBM Linux Technology Center Open Hypervisor Team email: eak@us.ibm.com