Re: additional esx events (was Re: [PATCH] VMware Balloon: rename module)

[Dmitry Torokhov <dtor@vmware.com>]

[BCC-ing akpm and LKML since they are probably not interested in ESX too much]

On Thursday, September 16, 2010 07:37:24 pm Chetan Loke wrote:
> On Thu, Sep 16, 2010 at 8:31 PM, Dmitry Torokhov <dtor@vmware.com> wrote:
> 
> > There is vSphere SDK that shoudl allow you to connect to the hostd and
> > get more information about the host/VC:
> > 
> > http://www.vmware.com/support/developer/viperltoolkit/
> 
> perl API? why? vmware_balloon driver already has the hooks. So a
> parallel driver can have the same
> basic implementation. I'm not looking for any fancy notifications.
> Even if we emit sysfs nodes, it's
> perfectly fine. It will be a one-way read only channel.I am willing to test
> it.

I do not understand why we should try jamming into the kernel something that
can be implemented in userspace. Balloon is in the kernel because it is
privileged operation that affects correctness of the VM handling (if we are
told that certain page can be ballooned and it was a lie VM may crash), but
monitoring-type application can and should use different communication
channels.

Thanks.

-- 
Dmitry