From owner-freebsd-virtualization@freebsd.org Sun Feb 24 14:52:31 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 476B6150043F for ; Sun, 24 Feb 2019 14:52:31 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 3CC70700E0 for ; Sun, 24 Feb 2019 14:52:27 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=bV0vBmOqyBzKbJ3qmguWhTBPp/a9th7kiROEGI38BYw=; b=j76sJPUY/mq70QF5KzPj12LJ0Q BCWSTtfXQy4iS8fN/5xk8oeKauvPTjr8XLCQVehNcCRrJ5oCisSJ1GslE2WbK7F3sjnN3Qxyo7Cyl j1aJLfpOsRsMVBOzscmEXa3//sAYvXlJ8n1ZE7fREctt3i8osRq+pAgtyfoaa58veQPw=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1gxv8k-000Jpm-1H for freebsd-virtualization@freebsd.org; Sun, 24 Feb 2019 21:52:26 +0700 Date: Sun, 24 Feb 2019 21:52:26 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: NVMe and Bhyve Message-ID: <20190224145226.GA76175@admin.sibptus.ru> References: <20190212130506.GA62989@admin.sibptus.ru> <20190215044134.GA52633@admin.sibptus.ru> <20190216041134.GA75357@admin.sibptus.ru> <20190217155811.GA99389@admin.sibptus.ru> <20190218010901.GA8125@admin.sibptus.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.2 (2019-01-07) Sender: Victor Sudakov 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, 24 Feb 2019 14:52:31 -0000 Jason Tubnor wrote: > > > > > Well, disk0 will be the guest HDD to install to, disk1 will be the ISO with > > drivers, and which disk will be the ISO attached by the "vm install" > > command? > > > > > From a user perspective, this is not of any value to know. vm-bhyve > manages that in the background and usually puts the regular disk0 as -s 4:0 > regardless of normal boot or install and when the installer is invoked, > puts the installer iso in as -s 3:0 Oh, if vm-bhyve manages that the installer ISO is always attached before other ancillary ISOs, that's fine with me. > > So based on previous examples, you'd see something like this in the log: > -s 3:0,ahci-cd,/vm/.iso/myinstaliso.iso -s > 4:0,ahci-hd,/dev/zvol/mypool/vm/myserver/disk0 -s > 5:0,ahci-cd,/vm/myserver/virtio-win-0.1.164.iso I see. I have tried this and it works as you describe, which is good news. However, there is bad news too. I've tried to install Windows 10 and Windows Server 2012R2 onto the virtio-blk device, but... The guest installer says that there are no disks to install to and no drivers, and suggests a driver to be loaded. It can be told to find the appropriate driver in my virtio-win-0.1.141.iso CD: http://admin.sibptus.ru/~vas/bhyve1.png but when it begins loading the viostor driver, the VM crashes with "bhyve exited with status 134" Therefore I ask again if someone has an actual success story of running a Windows guest on a virtio-blk device. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/