[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [Libvir] The problem of the definition of tuning informations
- From: Daniel Veillard <veillard redhat com>
- To: beth kon <eak us ibm com>
- Cc: libvir-list redhat com
- Subject: Re: [Libvir] The problem of the definition of tuning informations
- Date: Thu, 8 Nov 2007 16:59:39 -0500
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 redhat com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]