On 2019/01/22 09:53, Giovanni Bechis wrote: > >>> Description: > >> On Vsphere 6.0 an OpenBSD guest does recognizes the second cpu but it > >> cannot put it online > >> The host uses an AMD cpu > >>> How-To-Repeat: > >> Start a vm on Vsphere 6.0 with smt disabled > >>> Fix: > >> setting hw.smt=1 is a workaround, a reboot is not needed > > > > By "with smt disabled" are you talking about disabling vmware's smt support > > (System, Advanced System Settings, VMkernel.Boot.hyperthreading) or are you > > talking about changing the settings for the individual vm (Configure, > > Hardware, Processors, and set as multiple cores *not* multiple "logical > > processors")? > > > VMkernel.Boot.hyperthreading is enabled on Vsphere, I tried setting both 2 > cores with 1 logical processor and 1 core with 2 logical processor > but it acts the same.
Thanks, that does seem like a vmware bug then. It's worth trying changing it to 1 core per socket, this seems more likely to work (to my eyes it is a hack for changing the topology presented to guest OS to "help" people with per-socket-licensed software, so I guess vmware paying customers are more likely to whine if it's broken ;-)
