> In my testing, this has no effect on the operation of the clock. Only
> the guest OS selected in the VM configuration does have an effect.
> We should remove any suggestion that 32bit FreeBSD is the right thing
> to select though, so changing the guest OS we report is still a good
> idea.
> Interestingly, it looks like if the guest OS is set to 'Other
> (64-bit)', and vmt reports an unrecognised short guest OS name (such
> as 'OpenBSD'), vcenter will display the full guest OS name, so you
get > something like 'OpenBSD 7.2 GENERIC.MP#31'.
> I'm pretty sure this caused problems in the distant past, but it seems
> fine now with esxi 6.7+, so I think we should change to saying we're
> OpenBSD instead.
Replacing 'FreeBSD' with something ESXi doesn't support will almost
certainly have drawbacks. We can already see different 'Guest OS'
options have different effects on guest VMs.
Also, OpenBSD really is part of BSD family.
I have an OpenBSD VM running without issues as a guest with 'FreeBSD'
option for years and serving as an Internet router for home network.
IMO, it's pretty good chice.
Only thing I would update is to make it exactly specify to hypervisor is
it 32 or 64 bit OS. So 'FreeBSD-64' for amd64 and 'FreeBSD' for i386.
