From owner-freebsd-virtualization@freebsd.org Fri Feb 15 23:48:24 2019 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 504C214EDFC1 for ; Fri, 15 Feb 2019 23:48:24 +0000 (UTC) (envelope-from stb@lassitu.de) 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 475538C2E4 for ; Fri, 15 Feb 2019 23:48:23 +0000 (UTC) (envelope-from stb@lassitu.de) Received: by mailman.ysv.freebsd.org (Postfix) id 07BFE14EDFBF; Fri, 15 Feb 2019 23:48:23 +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 E97E014EDFBE for ; Fri, 15 Feb 2019 23:48:22 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2a00:14b0:4200:32e0::1ea]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gilb.zs64.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88BF48C2E3 for ; Fri, 15 Feb 2019 23:48:22 +0000 (UTC) (envelope-from stb@lassitu.de) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 92B431F1F4F; Fri, 15 Feb 2019 23:48:19 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: NVMe and Bhyve From: Stefan Bethke In-Reply-To: <20190215044134.GA52633@admin.sibptus.ru> Date: Sat, 16 Feb 2019 00:48:17 +0100 Cc: "freebsd-virtualization@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <20190207174453.Horde.hWBGfoLlymCpipxLv8WUJo9@app.eeeit.de> <5121268a-1ead-9858-86a7-27f75048feb2@yuripv.net> <20190212084333.GA46685@admin.sibptus.ru> <20190212130506.GA62989@admin.sibptus.ru> <20190215044134.GA52633@admin.sibptus.ru> To: Victor Sudakov X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: 88BF48C2E3 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.97)[-0.972,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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: Fri, 15 Feb 2019 23:48:24 -0000 > Am 15.02.2019 um 05:41 schrieb Victor Sudakov : >=20 > Jason Tubnor wrote: >>=20 >>> If you have Nvme devices or you want store disks in ram yes, = otherwise no. >>>=20 >>>>=20 >>>> Is it worth it? I mean upgrading from 11.2-RELEASE to 12.0-RELEASE = for >>>> the sake of nvme, is it useful for running FreeBSD, Linux (Mint, >>>> Centos) and Windows10 guests? >>>>=20 >>=20 >>=20 >> Or if you are using good SLOG and ARC for your VM zvols. >>=20 >> I'm still sorting out some Windows issues with the bhyve nvme = presentation >> for a variety of guest (except freebsd, that works fine) at the = moment. I >> would avoid 12.0-RELEASE as it may introduce other issues with your >=20 > I was just worried that using ahci-hd instead of paravirtualized disks > causes suboptimal performance of guests. Do you think there is a hope = to get > paravirtualized disks support for Windows guests in bhyve? I was under the impression that the Windows VirtIO disk driver works = with the Bhyve virtio-blk device. You need to provide these drivers to = Windows somehow (for example, as a second CD image during installation): = https://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers Stefan --=20 Stefan Bethke Fon +49 151 14070811