Date: Tue, 1 Nov 2016 09:02:57 +0000 From: Matt Churchyard <matt.churchyard@userve.net> To: The Doctor <doctor@doctor.nl2k.ab.ca> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: RE: Windows 2016 Message-ID: <ec0716c52aeb4ea18d09b193ac61b493@SERVER.ad.usd-group.com> In-Reply-To: <20161101044503.GA58756@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
>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. 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ec0716c52aeb4ea18d09b193ac61b493>