Re: "right" way to gather domU stats in xen 3 & 4?

[Florian Heigl <florian.heigl@gmail.com>]

Hi Dan,

2011/3/1 Dan Magenheimer <dan.magenheimer@oracle.com>:
> Tmem has no value without guest kernel changes and getting those
> changes (even though very small) into the Linux kernel has proven
> to be a very long frustrating experience, which I hope will

I wondered for some time now... can't you just push it into Oracle VM
& OEL in the meantime?
Even as an unsupported kernel, It would "work for me" and my customers.

About the long frustrating experience, see my sig :)

> A couple of key things to plan for in your management tools:
> 1) Don't assume that the amount of memory used by a guest is
>   fixed and/or only under the control of your tools.

Thats why I've been asking so intently. Right now it will be great to
have a graph showing mem and maxmem, but when tmem is seeing more
adaption any baloon stats become less useful.
Also, as of today, half of the distros doesn't have working cpu
hotplug or balooning anyway.


Anyway, thanks for the update :)
Flo


-- 
the purpose of libvirt is to provide an abstraction layer hiding all
xen features added since 2006 until they were finally understood and
copied by the kvm devs.