Signed-off-by: Jim Meyering [EMAIL PROTECTED]
---
ChangeLog |4
src/virsh.c | 10 +-
2 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index ce68401..a6de485 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2007-11-08 Jim Meyering
I promised that mail for the beginning of the week but I still have
a very hard time to try to formulate a good plan of action, I'm still
stuck in a dilemna, see below.
What is it?
---
I think tuning informations are that set of parameters associated
to a domain or a host, which are not
On Thu, Nov 08, 2007 at 06:43:41PM +0100, Jim Meyering wrote:
I stumbled across two more missing printf attributes:
2007-11-08 Jim Meyering [EMAIL PROTECTED]
* src/virsh.c (vshPrintExtra, vshDebug): Use gcc's printf attribute.
Attaching differently, in an attempt to defy
Florian Forster wrote:
Hi Rich,
as promised, I've taken a more in-depth look at the `libvirtstats'
plugin (I've adopted this as a working title for now and will do the
renaming on the weekend or so..) and it looks very good, thanks again :)
The `_virDomainInfo' structure has the members
On Thu, Nov 08, 2007 at 02:00:10PM -0600, Ryan Harper wrote:
* Daniel Veillard [EMAIL PROTECTED] [2007-11-08 10:08]:
I promised that mail for the beginning of the week but I still have
I think tuning informations are that set of parameters associated
to a domain or a host, which are not
On Thu, Nov 08, 2007 at 03:41:12PM -0600, Ryan Harper wrote:
* Daniel Veillard [EMAIL PROTECTED] [2007-11-08 15:27]:
yes, I understand and that's why I agreed to add the cpuset information
at that point it's more than tunning because it may be irreversible for the
lifetime of the domain,
On Thu, Nov 08, 2007 at 02:34:05PM -0500, beth kon wrote:
Daniel Veillard wrote:
snip
My opinion:
---
We need better tools, even for simple use case to be able to save
an existing tuning for a domain or a full machine, and reload it
when needed. This is IMHO better done
* Daniel Veillard [EMAIL PROTECTED] [2007-11-08 10:08]:
I promised that mail for the beginning of the week but I still have
I think tuning informations are that set of parameters associated
to a domain or a host, which are not stricly needed to get the
domain(s) working but improve their
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,
Daniel Veillard wrote:
snip
My opinion:
---
We need better tools, even for simple use case to be able to save
an existing tuning for a domain or a full machine, and reload it
when needed. This is IMHO better done on top of the existing API
which already have the entry points to
* Daniel Veillard [EMAIL PROTECTED] [2007-11-08 15:27]:
On Thu, Nov 08, 2007 at 02:00:10PM -0600, Ryan Harper wrote:
* Daniel Veillard [EMAIL PROTECTED] [2007-11-08 10:08]:
I promised that mail for the beginning of the week but I still have
I think tuning informations are that set of
11 matches
Mail list logo
