On 11/09/16 03:24, Bryan Vyhmeister wrote: > On Tue, Nov 08, 2016 at 09:57:29PM +0300, Alexei Malinin wrote: >>> Synopsis: Wrong Guest OS type in VMware ESXi 5.5.0.3568722 >>> Description: >> OpenBSD kernel reports wrong Guest OS type to VMware ESXi. >>> Fix: >> Maybe somewhere in sys/dev/pv/hyperv.c: hv_fake_version()... > The sys/dev/pv/hyperv.c driver is for running OpenBSD under HyperV, not > VMware. It's the vmt(4) driver you are looking for. Starting on line 522 > of sys/dev/pv/vmt.c, there is a comment: > > "Host doesn't like it if we send an OS name it doesn't > recognise, so use the closest match, which happens > to be FreeBSD." > > I am not sure why vmt(4) reports as 32-bit rather than 64-bit but that > doesn't really matter. The root cause is that VMware does not support > OpenBSD as a officially supported guest operating system. This would > make a difference if there were VMware Tools from VMware but since > vmt(4) is implementing the required functions, it doesn't really matter. > OpenBSD works just fine under VMware ESXi and I have been using it that > way for at least six years running as "Other (64-bit)" before vmt(4) was > available.
Thank you for the explanation, Bryan. "32-bit" confused me, and I tried to find where I could change "32" to "64" but I couldn't - should I hack vmware tools? -- Alexei Malinin
