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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTimFUgZoKBXk_weOG_AMtW8Y0g6Q8-QvH8hnfv8z@mail.gmail.com>
Date:	Thu, 16 Sep 2010 22:37:24 -0400
From:	Chetan Loke <chetanloke@...il.com>
To:	Dmitry Torokhov <dtor@...are.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"pv-drivers@...are.com" <pv-drivers@...are.com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
Subject: additional esx events (was Re: [PATCH] VMware Balloon: rename module)

On Thu, Sep 16, 2010 at 8:31 PM, Dmitry Torokhov <dtor@...are.com> wrote:
>> >> side note - is it possible to extend the balloon driver to get a
>> >> notification on other events? like CPUs, NICs? Just an event is what
>> >> I'm looking for. No action need to be taken in the guest.
>> >
>> > No, balloon driver should be limited to ballooning. I think the data
>> > you are looking for can be retrieved via GuestSDK (and I believe we
>> > are adding balloon_target to the available data).
>>
>> No. I think the guestSDK provides the guest, it's personal view of the
>> world, no?
>> http://www.vmware.com/support/developer/guest-sdk/
>
> Right since guest is supposed to be isolated.

pv != isolation and ballooning isn't either ;). But let's not get into that.


>
> 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.

>
>>
>> ballooning is an indirect hint that an external event has happened
>> within the hypervisor. I'm looking for similar external events.
>> guestSDK gives nothing. Because right now there is now way for a
>> vmware-guest to cooperate or be a good citizen if it
>> doesn't know what's happening in the esx-hypervisor. Now whether to
>> add these events in the balloon driver is another thing.
>> A separate driver is ok too.
>
> I spoke with resource management team regarding this idea of a VM
> "helping" ESX and they felt that this task is better left to the
> ESX's memory scheduler. The VM in question will not know all the
> data needed (it might be confined to a separate resource pool, etc)
> to make good decision.

ok, so its not just about freeing resources but I've agents(within
VMs) running on esx hypervisor.
So by getting CPU/NIC/Memory events I can log those and raise soft alarms to
a central monitoring node.


>
> Still you could use Guest SDK - if you see balloon target rising you
> may start unlocking memory you grabbed.
>
ballooning does nothing to guests who have mmap'd memory and drivers
who have pinned down pages.
And forcibly releasing(aka soft illegal OOM?) someone else's mmap'd
memory will never be allowed.
Anyways, the use case is also for monitoring and not just for freeing resources.


> Dmitry

regards
Chetan Loke
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/