From owner-freebsd-virtualization@freebsd.org Sun Nov 4 21:01:33 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5FE610EBA47 for ; Sun, 4 Nov 2018 21:01:33 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 151E98640A for ; Sun, 4 Nov 2018 21:01:33 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id CE40C10EBA34; Sun, 4 Nov 2018 21:01:32 +0000 (UTC) Delivered-To: virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9452710EBA33 for ; Sun, 4 Nov 2018 21:01:32 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1773C862E5 for ; Sun, 4 Nov 2018 21:01:32 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 4ABF61704A for ; Sun, 4 Nov 2018 21:01:31 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id wA4L1VxW045662 for ; Sun, 4 Nov 2018 21:01:31 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id wA4L1V4o045657 for virtualization@FreeBSD.org; Sun, 4 Nov 2018 21:01:31 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201811042101.wA4L1V4o045657@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: virtualization@FreeBSD.org Subject: Problem reports for virtualization@FreeBSD.org that need special attention Date: Sun, 4 Nov 2018 21:01:31 +0000 MIME-Version: 1.0 X-Rspamd-Queue-Id: 151E98640A X-Spamd-Result: default: False [-3.09 / 200.00]; ARC_NA(0.00)[]; FORGED_RECIPIENTS_FORWARDING(0.00)[]; FORWARDED(0.00)[virtualization@mailman.ysv.freebsd.org]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_DN_NONE(0.00)[]; HAS_XAW(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; URI_COUNT_ODD(1.00)[3]; RCPT_COUNT_ONE(0.00)[1]; SPF_FAIL_FORWARDING(0.00)[]; DMARC_NA(0.00)[FreeBSD.org]; RCVD_IN_DNSWL_MED(-0.20)[5.0.0.0.0.5.0.0.0.0.0.0.0.0.0.0.a.6.0.2.4.5.2.2.0.0.9.1.1.0.0.2.list.dnswl.org : 127.0.9.2]; MX_GOOD(-0.01)[cached: mx1.FreeBSD.org]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.92)[-0.921,0]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; IP_SCORE(-2.95)[ip: (-9.19), ipnet: 2001:1900:2254::/48(-3.21), asn: 10310(-2.30), country: US(-0.07)]; ASN(0.00)[asn:10310, ipnet:2001:1900:2254::/48, country:US]; FORGED_RECIPIENTS(0.00)[virtualization@FreeBSD.org,freebsd-virtualization@freebsd.org]; RCVD_COUNT_SEVEN(0.00)[7]; TO_DOM_EQ_FROM_DOM(0.00)[] X-Rspamd-Server: mx1.freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Nov 2018 21:01:33 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 230773 | [bhyve] GDT limit needs reset on VMX exit 1 problems total for which you should take action. From owner-freebsd-virtualization@freebsd.org Tue Nov 6 17:25:49 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A21F112AACD for ; Tue, 6 Nov 2018 17:25:49 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from potato.growveg.org (potato.growveg.org [82.70.91.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0E4D7816D9 for ; Tue, 6 Nov 2018 17:25:46 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from parsley.growveg.org ([82.70.91.97] helo=desktop.local) by potato.growveg.org with esmtp (Exim 4.91 (FreeBSD)) (envelope-from ) id 1gK56g-0000bY-8Z for freebsd-virtualization@freebsd.org; Tue, 06 Nov 2018 17:25:38 +0000 Date: Tue, 6 Nov 2018 17:25:35 +0000 From: tech-lists To: freebsd-virtualization@freebsd.org Subject: is there a vCPU hard limit for bhyve guests? Message-ID: <20181106172535.20e46ef6@desktop.local> Organization: zyxst.net X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 0E4D7816D9 X-Spamd-Result: default: False [2.12 / 200.00]; ARC_NA(0.00)[]; R_SPF_NEUTRAL(0.00)[?all]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.27)[0.265,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[zyxst.net]; NEURAL_SPAM_MEDIUM(0.40)[0.399,0]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_LAST(0.00)[]; MX_GOOD(-0.01)[in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com]; NEURAL_SPAM_LONG(0.58)[0.583,0]; IP_SCORE(-0.01)[country: GB(-0.07)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:13037, ipnet:82.68.0.0/14, country:GB]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Nov 2018 17:25:49 -0000 Hi, On a host with hw.ncpu=48 I tried to start a bhyve guest with -c 24 and it failed to start. So I tried -c 16 and it starts and runs as expected. Any more than -c 16 fails to run. Is a maximum of 16 vCPU hardwired somewhere, and if so, why? Is there a way to overcome the limit? thanks, -- J. From owner-freebsd-virtualization@freebsd.org Wed Nov 7 00:15:20 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AACC711062B7 for ; Wed, 7 Nov 2018 00:15:20 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.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 CCA8B77516 for ; Wed, 7 Nov 2018 00:15:19 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id wA703JAA098311; Tue, 6 Nov 2018 16:03:19 -0800 (PST) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id wA703H1Q098310; Tue, 6 Nov 2018 16:03:17 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201811070003.wA703H1Q098310@pdx.rh.CN85.dnsmgr.net> Subject: Re: is there a vCPU hard limit for bhyve guests? In-Reply-To: <20181106172535.20e46ef6@desktop.local> To: tech-lists Date: Tue, 6 Nov 2018 16:03:17 -0800 (PST) CC: freebsd-virtualization@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: CCA8B77516 X-Spamd-Result: default: False [2.19 / 200.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.51)[0.508,0]; NEURAL_HAM_LONG(-0.31)[-0.306,0]; 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.12)[0.120,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: pdx.rh.CN85.dnsmgr.net]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.02)[country: US(-0.08)] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2018 00:15:20 -0000 > Hi, > > On a host with hw.ncpu=48 I tried to start a bhyve guest with -c 24 and > it failed to start. So I tried -c 16 and it starts and runs as > expected. Any more than -c 16 fails to run. > > Is a maximum of 16 vCPU hardwired somewhere, and if so, why? Is there a > way to overcome the limit? man bhyve Look at -c option, default is 1 max is 16. There is a compile time constant VM_MAXCPU, you can raise that to 20, then other problems come about that require more patching. Last time I played with this it failed above 16, I suspect some other places have had a bad derived constant using the assumption that 16 is the max. > thanks, > -- > J. > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" > -- Rod Grimes rgrimes@freebsd.org