From owner-freebsd-virtualization@freebsd.org Mon Feb 18 02:33:05 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 B7C5714EE1C9 for ; Mon, 18 Feb 2019 02:33:05 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) 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 230DD6F3A8 for ; Mon, 18 Feb 2019 02:33:05 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: by mailman.ysv.freebsd.org (Postfix) id DA07714EE1C5; Mon, 18 Feb 2019 02:33:04 +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 C7BCF14EE1C4 for ; Mon, 18 Feb 2019 02:33:04 +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 1F5D56F3A3 for ; Mon, 18 Feb 2019 02:33:03 +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 x1I2WrhA003254; Sun, 17 Feb 2019 18:32:53 -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 x1I2Wr6N003253; Sun, 17 Feb 2019 18:32:53 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201902180232.x1I2Wr6N003253@pdx.rh.CN85.dnsmgr.net> Subject: Re: NVMe and Bhyve In-Reply-To: To: Jason Tubnor Date: Sun, 17 Feb 2019 18:32:53 -0800 (PST) CC: Victor Sudakov , "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: 1F5D56F3A3 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.977,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: Mon, 18 Feb 2019 02:33:05 -0000 > On Mon, 18 Feb 2019 at 02:58, Victor Sudakov wrote: > > > > > Or at least please tell me how I can attach another iso image (with > > drivers) when running "vm install myhost windows.iso" > > > Technically, you should be able to define something like: > > disk1_type="ahci-cd" > disk1_name="virtio-win-0.1.164.iso" > disk1_dev="file" or disk1_dev="custom" if you wish to use a path in disk1_name, I still do not know why this needs to be treated differently, a path should just work :-( > in the vm.conf file if the virtio-win-0.1.164.iso is located in > /vm/servername/ directory. -- Rod Grimes rgrimes@freebsd.org