Re: The problem of the definition of tuning informations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Nov 08, 2007 at 04:31:49PM -0500, Daniel Veillard wrote:
> On Thu, Nov 08, 2007 at 02:34:05PM -0500, beth kon wrote:
> > Just to be sure I understand, are you suggesting removing tuning 
> > information from any configuration file and making it a runtime exercise 
> > to set it up? (That is, after the domain has been started)
> 
>   It would not be removing, as I don't think we have any at this point,
> the only exception would be the 'currentMemory' parameter, and the cpuset
> informations, both are optional obviously, but may be absolutely necessary
> at creation time, to avoid a broken or failed setup of the domain.

  Hum, I'm afraid I may have been unclear there, currentMemory and cpuset
aren't really tuning parameters and need to be stay in the XML config.
They are just 2 inforamtions which are on the edge.

Daniel

-- 
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard      | virtualization library  http://libvirt.org/
veillard@xxxxxxxxxx  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine  http://rpmfind.net/

--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]