From owner-freebsd-hackers@freebsd.org Tue Nov 26 21:25:54 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6EBBD1C1D6B for ; Tue, 26 Nov 2019 21:25:54 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47Mxlj2V7sz4HRf for ; Tue, 26 Nov 2019 21:25:52 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id xAQLPnm4004542; Tue, 26 Nov 2019 13:25:49 -0800 (PST) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id xAQLPnwU004541; Tue, 26 Nov 2019 13:25:49 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201911262125.xAQLPnwU004541@gndrsh.dnsmgr.net> Subject: Re: Nothing is broken, but changed WAS: what's got broken in bhyve after upgrade In-Reply-To: To: Wojciech Puchar Date: Tue, 26 Nov 2019 13:25:49 -0800 (PST) CC: "Rodney W. Grimes" , freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 47Mxlj2V7sz4HRf X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [2.15 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.70)[0.697,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.52)[0.519,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.04)[ip: (0.14), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.03), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2019 21:25:54 -0000 Almost forgot, be sure you install it to /usr/include before trying to compile stuff, you may end up picking up old values unless you use buildworld. cp /usr/src/sys/amd64/include/vmm.h /usr/include/machine/vmm.h > 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@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" > >>> > >>> > >> _______________________________________________ > >> 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" > >> > > > > -- > > Rod Grimes rgrimes@freebsd.org > > > > > _______________________________________________ > 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" > -- Rod Grimes rgrimes@freebsd.org