From owner-freebsd-virtualization@freebsd.org Tue Nov 1 14:16:16 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 54CF7C285BC for ; Tue, 1 Nov 2016 14:16:16 +0000 (UTC) (envelope-from daniel.tihanyi@tetragir.com) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 140DA1D08 for ; Tue, 1 Nov 2016 14:16:15 +0000 (UTC) (envelope-from daniel.tihanyi@tetragir.com) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 97032206DA for ; Tue, 1 Nov 2016 10:16:14 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 01 Nov 2016 10:16:14 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=tetragir.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=ipJmIl+4HGwvTae pfsYvWVrOIpE=; b=PtEuz49gecKxzDcuV3xviixR6vzc7sa3TRWvxlj5v853zGY QMWVpWQAqbiTkkx26BwhIObfwKIMvR4v4etHBnE1BShO6qHL5gBjrn4uF2c7qk+L d+oh5N2ZAR8kGqz4Z3QH/R8WB0d/cbD4uFnUYGshieBeVMf13XiUwy0YBEf4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=ipJmIl+4HGwvTaepfsYvWVrOIpE=; b=mJ6GM8ct1gP5+ARN6YwL Ejt7I/U7SAYyvO6YZFZNkacicjcoDUSFjvmas94OFVw1sRvkWXpX/fpXZT88nYNc ZVft0FG3ZTjzBLRKRpimh2VLwlWsSHeEzQcstMSXzsmYDqASFaaWtA0uXZMypLT7 Z/PBnhHuPGTXpMTM2HhpWaw= X-ME-Sender: X-Sasl-enc: Q+5pm/n9MjynY1FNtElqASiKaIxlDWRGrdRFJX12UZNX 1478009774 Received: from [10.25.249.127] (pd95c0bdc.dip0.t-ipconnect.de [217.92.11.220]) by mail.messagingengine.com (Postfix) with ESMTPA id F00A5F29C9 for ; Tue, 1 Nov 2016 10:16:13 -0400 (EDT) Message-ID: <1478009772.19546.74.camel@fastmail.fm> Subject: Re: Windows 2016 From: Daniel Tihanyi To: freebsd-virtualization@freebsd.org Date: Tue, 01 Nov 2016 15:16:12 +0100 In-Reply-To: <20161101140249.GB27402@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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: Tue, 01 Nov 2016 14:16:16 -0000 On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: > > > > > > > > I was able to install the Windows 2016 using the GUI method. > > > > > > One problem. > > > > > > It is assigned an IP but > > > > > > the netmask and the default route is not showing up. > > > > > > Also  The virtual Windows 2016 box does not see a network > > > interface. > > This makes very little sense. You usually specify the netmask and > > default route when you assign Windows an IP address. > > And how have you assigned the guest an IP address if it has no > > network interface? > > > The taps are allocated an IP address. > > I fully concur. > > In the install at one point, I declare that the IP address, netmask > and gateway > are 'declared' at the 'MB ' BIOS interface. > > > > > > > > > > What must I do to convince this box that is it on a switch > > On the bhyve host it should be configured just like any other bhyve > > virtual machine. The guest should have a virtio-net device, which > > is linked to a tap interface on the host. That tap interface should > > be bridged with whichever physical network adapter you want the > > guest connected to. > > > > However, I think I mentioned in a previous message that Windows > > does not have the virtio-net drivers by default. You need to boot > > the guest with the virtio-net driver ISO attached and install the > > driver. You should see the interface in Device Manager flagged as > > not installed/working. > > > > That is correct . > > I do have an iso of the MB drivers, > > namely a Supermicro  X10DRW-i MB  > > and  > > from Intel I did obtain the .exe file for the i350GbE drivers. > I script a 2 phase installation as follows: > > 1) > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- > hd,windows2016.img -s 5,virtio-net,tap15 -s > 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet -s 31,lpc > -l com1,stdio -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > windows2016guest > > 2) > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/null-install.iso > -s 4,ahci-hd,windows2016.img -s 5,virtio-net,tap15 -s > 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s 30,xhci,tablet -s > 31,lpc -l com1,/dev/nmdm15A -l bootrom,/usr/local/share/uefi- > firmware/BHYVE_UEFI.fd windows2016guest & > > As I said, I have picked up an ISO from the MB manufacturer > > let's call it manufacturer.iso . > > Where do I place said iso in the 'phase' of things? You use virtio network adapters, you have to install the virtio drivers and NOT the drivers for the physical interface. Then configure the IP Address, gateway, etc. in Windows.