Gotcha. Requiring a pkg_add and rcctl basically makes it inline with every other OS that reports to VMWare; having a kernel driver is the exception rather than the rule. I don't have any issues with the solution as long as I can get proper metadata reported to vCenter. Is the port available for me to test on my end? Do I need to grab the ports tree from source and compile from there or is it already available via pkg_add?
Cheers, Alex On Fri, Jan 8, 2021, at 12:29 PM, Klemens Nanni wrote: > On Fri, Jan 08, 2021 at 11:58:25AM -0700, Alex Long wrote: > > Okay. So going forward, vmt(4) is being deprecated in favor of the new > > open-vm-tools port? > The package can do everything the driver does and more, but it also > requires pkg_add and rcctl to work opposed to just a default base > installation in order to automatically provide basic information to the > host. > > Since package and driver do not seem to conflict according to my tests, > there's no need to directly remove vmt(4) after importing the package. > > In the long run however --if there are no problems with open-vm-tools > on OpenBSD-- I don't see why we should keep and maintain our own driver. > > vmt(4) came to be before open-vm-tools was a thing and until now noone > simply ported it to OpenBSD; other than that, there seem to be no > specific reasons not to use upstream's code. >
