From owner-freebsd-virtualization@freebsd.org Tue Nov 1 09:21:28 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 8DA15C281D0 for ; Tue, 1 Nov 2016 09:21:28 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-outbound.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2916914A8 for ; Tue, 1 Nov 2016 09:21:27 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) by smtp-outbound.userve.net (8.15.1/8.15.1) with ESMTPS id uA19L9aP057405 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 1 Nov 2016 09:21:13 GMT (envelope-from matt.churchyard@userve.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1477992073; bh=dVB2bkB0ebHMqyAVNBpAHaNb7bSL/vtbitT1VIEgFwc=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=HdBhkuMJgm6U0JPFB0/MGa1HRQ7ypPcNUaXBmxsXkpqWNmbuoVFjDyYOz1UBd9PzQ UyGq1zFRWosr4sQ6KU+5aRtmzAtDQKy9HHILvVl+52ZKHaLNs3ukj2VJ3squHlKdxT WrF1PYFkAz8/EOzDA1qt2R/M7/T3QZy81VXWZr9A= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 1 Nov 2016 09:21:03 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Tue, 1 Nov 2016 09:21:03 +0000 From: Matt Churchyard To: "freebsd-virtualization@freebsd.org" Subject: RE: Windows 2016 Thread-Topic: Windows 2016 Thread-Index: AQHSM/rIdWE82Qm9HE2AlMaCqt5JpKDD05awgAAFgeA= Date: Tue, 1 Nov 2016 09:21:02 +0000 Message-ID: <51a088cbe3964542aec18bf6f1f2c4af@SERVER.ad.usd-group.com> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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 09:21:28 -0000 >I was able to install the Windows 2016 using the GUI method. >One proble. >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 r= oute when you assign Windows an IP address. And how have you assigned the guest an IP address if it has no network inte= rface? >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 t= ap interface on the host. That tap interface should be bridged with whichev= er physical network adapter you want the guest connected to. However, I think I mentioned in a previous message that Windows does not ha= ve the virtio-net drivers by default. You need to boot the guest with the v= irtio-net driver ISO attached and install the driver. You should see the in= terface in Device Manager flagged as not installed/working. -------------------------------------------- Just one other thing to add to this. I'm not sure if this is the case here,= but it's something I've seen a few times now. When configuring IP addresses, etc for a guest, this should be done -inside= - the guest. Do not assign a guest's IP address to the host, or to the tap interface. Bhyve works just like any other hypervisor. IP settings are done in the gue= st as if it was a real machine, the host just acts like a switch. -------------------------------------------- Matt >192.168.0.60 >Thar is handling the default routing to the interent. >For argument sake , >the Windows server is IP as 192.168.0.68 >I have an ubuntu up at 192.168.0.57 >a Centos at 192.168.0.54 >and >Fedora at 192.168.0.53 >all running successfully.