Date: Tue, 26 Nov 2019 10:44:40 +0100 (CET) From: Wojciech Puchar <wojtek@puchar.net> To: Wojciech Puchar <wojtek@puchar.net> Cc: freebsd-hackers@freebsd.org Subject: Nothing is broken, but changed WAS: what's got broken in bhyve after upgrade Message-ID: <alpine.BSF.2.20.1911261043410.71971@puchar.net> In-Reply-To: <alpine.BSF.2.20.1911260758100.3103@puchar.net> References: <alpine.BSF.2.20.1911260758100.3103@puchar.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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? 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@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@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1911261043410.71971>