From owner-freebsd-virtualization@freebsd.org Sat Oct 1 22:40:47 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D41DA946A1 for ; Sat, 1 Oct 2016 22:40:47 +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 CF0451D7; Sat, 1 Oct 2016 22:40:46 +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 u91Medo5051023; Sat, 1 Oct 2016 15:40:39 -0700 (PDT) (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 u91MeQlZ051020; Sat, 1 Oct 2016 15:40:26 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201610012240.u91MeQlZ051020@pdx.rh.CN85.dnsmgr.net> Subject: Re: couple of issues with bhyve windows 10 pro guest on FreeBSD 11.0 In-Reply-To: To: Peter Grehan Date: Sat, 1 Oct 2016 15:40:26 -0700 (PDT) CC: Tao Zhen , 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-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sat, 01 Oct 2016 22:40:47 -0000 ... > bhyve can be configured to expose vCPUs as logical processors within a > socket using tunables that should be set before vmm.ko is loaded (or > after unload/before reload). > > hw.vmm.topology.cores_per_package (defaults to 1) > hw.vmm.topology.threads_per_core ( " " ) > > Note that these settings are global and will be used by all VMs. To be more compatible with many other virtualization products how hard would it be to change these to per VM instance tunables? -- Rod Grimes rgrimes@freebsd.org