Nothing is broken, but changed WAS: what's got broken in bhyve after upgrade

[Wojciech Puchar]

thank you

On Tue, 26 Nov 2019, Rodney W. Grimes wrote:

>> New bhyve gets sockets, cores and threads parameters from command line.
>> fixed now.
>>
>> Question - is 16 core limit in bhyve a hard one because of something, or
>> it can be changed?
>
> Yes, modify this line:
> #define VM_MAXCPU       16                      /* maximum virtual cpus */
> in  ./amd64/include/vmm.h
>
> You'll need to rebuild vmm.,ko, and anything else that includes vmm.h
>
>
>> On Tue, 26 Nov 2019, Wojciech Puchar wrote:
>>
>>> upgraded to
>>>
>>> FreeBSD puchar.net 11.3-STABLE FreeBSD 11.3-STABLE #0 r354807: Fri Nov 22
>>> 22:45:43 CET 2019     root at puchar.net:/usr/src/sys/amd64/compile/puchar amd64
>>>
>>>
>>> i have setting hw.vmm.topology.cores_per_package=16 in loader.conf
>>>
>>>
>>> before upgrade - bhyve virtual machines (windows 7) see one CPU with 2 or 4
>>> cores (depending how much i use with -c option in bhyve).
>>>
>>> after upgrade - bhyve sees single core CPUs. Which in case of windows 7 pro
>>> means no more than 2 cores will be used.
>>>
>>> What's wrong and how to fix it?
>>>
>>> _______________________________________________
>>> freebsd-hackers at freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
>>>
>>>
>> _______________________________________________
>> freebsd-hackers at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
>>
>
> -- 
> Rod Grimes                                                 rgrimes at freebsd.org
>
>