From owner-freebsd-virtualization@freebsd.org Thu Apr 8 14:42:28 2021 Return-Path: Delivered-To: freebsd-virtualization@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 4A8815DE40A for ; Thu, 8 Apr 2021 14:42:28 +0000 (UTC) (envelope-from matt.home@userve.net) Received: from smtp-a.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.userve.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FGP9v1xVvz3LxF for ; Thu, 8 Apr 2021 14:42:26 +0000 (UTC) (envelope-from matt.home@userve.net) Received: from webmail.userve.net (unknown [192.168.100.200]) by smtp-a.userve.net (Postfix) with ESMTPA id 6CCAD238420 for ; Thu, 8 Apr 2021 15:42:18 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=uk1; t=1617892938; bh=IILIoVKu5dRDtuMoD9P8RlBNNji8Zd0QFIkU0I6LcvE=; h=Date:From:To:Subject; b=qQzclPqEpILIbTxvgWUByXcfIVej6WZu4m0dve43nVwOADK67wrowgsO4JMtsWfhF 05R6Me+T/Ut2kWBMgjFrLJi02Lgyu0Hf11rK52gJhLif2rOUEXMjAtzUq7iVd3EwSM pNdV/EPHG6m8CcOq4SGyS4AGrIuk488BJCPCNIyI= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 08 Apr 2021 15:42:18 +0100 From: Matt Churchyard To: freebsd-virtualization@freebsd.org Subject: bhyve current windows status User-Agent: Roundcube Webmail/1.4.0 Message-ID: <7850c18aba62e6150f227f3c1168974c@userve.net> X-Sender: matt.home@userve.net X-Rspamd-Queue-Id: 4FGP9v1xVvz3LxF X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=userve.net header.s=uk1 header.b=qQzclPqE; dmarc=none; spf=pass (mx1.freebsd.org: domain of matt.home@userve.net designates 217.196.1.22 as permitted sender) smtp.mailfrom=matt.home@userve.net X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[217.196.1.22:from]; R_DKIM_ALLOW(-0.20)[userve.net:s=uk1]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:217.196.1.0/24]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[217.196.1.22:from:127.0.2.255]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[userve.net:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_NA(0.00)[userve.net]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:20652, ipnet:217.196.0.0/20, country:GB]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-virtualization] X-Mailman-Approved-At: Thu, 08 Apr 2021 19:16:41 +0000 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.34 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: Thu, 08 Apr 2021 14:42:28 -0000 Hello, I'm after some general information on the current status/best practises for Windows on bhyve. Not entirely the correct place for this but then at the moment no-one else seems to really know the answers. Maybe I can help some of the other people who are just as unclear as me on what is actually the best information at this point. What are the current recommended devices/options for Windows (2019 server in my case) - especially with ZFS. Should I be specifying a 512/4096 sector/block size via bhyve and/or zfs? I assume nvme & virtio-net are the current best options but is there a preferred virtio driver version. Are any of the other virtio drivers of any use to be installed or just the network drivers? Are there any known problems with applications like AD/Exchange? I know that SQL 2012 had massive storage overhead issues on ZFS due to 512 byte writes, but I'm not sure if that still affects newer versions or other applications? The system I am currently using is a Xeon E5-2670, which I know was terrible before the TPR commit. My test system seems to run reasonably on 12.2 (although I'd be intruiged to compare against ESXi if I had the time), but do you think I would expect to see any significant gains by using a CPU with APICv? (not that I expect anyone has done any benchmarking of this) Are there any other changes in being worked on that are likely to have an impact on support or performance? I believe quite a bit of work is being done on the UEFI firmware but I expect that doesn't really affect much other than the boot process. I'm sure I saw reference to the devs having regular bhyve calls, but I have little idea what is currently being worked on. Thanks for any replies, Matt