This is a straight forward port that I've tested against ESXi 7.0U1:

        Information for inst:open-vm-tools-11.2.0

        Comment:
        Open VMware tools for VMware guests

        Description:
        open-vm-tools is a set of services and modules that enable several 
features in
        VMware products for better management of, and seamless user 
interactions with,
        guests. It includes kernel modules for enhancing the performance of 
virtual
        machines running Linux or other VMware supported Unix like guest 
operating
        systems.

        Maintainer: Klemens Nanni <k...@openbsd.org>

        WWW: https://github.com/vmware/open-vm-tools

With vmt(4) enabled (default), it is enough to do set basic values with
`vmware-rpctool "info-set ..."', i.e. `vmtoolsd' does not have to run.

With vm(4) disabled (`boot -c ; disable vmt ; exit') is it enough to
start the daemon in order to populate all relevant guestinfo values
including the IP addresses which vmt(4) currently does not work for
anymore.

I turned off basically all optional functionality for now to ease
initial porting, but that still leaves users the complete RPC client and
various features I could not test (yet).

All of the 39 patches consist of small hunks that basically add
a preprocessor check for OpenBSD in every place where FreeBSD already
has one - besides minor differences that were equally simple to adapt.

Those hunks that merely check for OpenBSD such that it bulds can be
upstreamed as is, the minority which change or implement behaviour
should get more looks and tests before trying to upstream them.

Select features such as the Wiper (wipe virtual disk via RPC) are
effectively NOOPs for now in so far as their init routines always return
false (for OpenBSD).

Once this is tested and in-tree, we can test and add more features one
by one;  X and therefore clipboard support for example seem handy.


Feedback? OK?

Attachment: open-vm-tools.tgz
Description: application/tar-gz

Reply via email to