Date: Tue, 1 Nov 2016 08:08:35 -0600 From: Randy Terbush <randy@terbush.org> To: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Windows 2016 Message-ID: <CALmWkDY9QdWOQJLUb3nu-7HS5DtXb5b8AANaAN0ZW92EH71ZnA@mail.gmail.com> In-Reply-To: <51a088cbe3964542aec18bf6f1f2c4af@SERVER.ad.usd-group.com> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <ec0716c52aeb4ea18d09b193ac61b493@SERVER.ad.usd-group.com> <51a088cbe3964542aec18bf6f1f2c4af@SERVER.ad.usd-group.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 1, 2016 at 3:21 AM, Matt Churchyard via freebsd-virtualization = < freebsd-virtualization@freebsd.org> wrote: > >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 > route when you assign Windows an IP address. > And how have you assigned the guest an IP address if it has no network > 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 link= ed > 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 t= he > virtio-net driver ISO attached and install the driver. You should see the > interface 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 > guest as if it was a real machine, the host just acts like a switch. > -------------------------------------------- > > =E2=80=8B > This issue may be unique to Windows 2016. =E2=80=8BI've had success installing most Windows releases with exception o= f Windows 2016. Windows 10 Enterprise and others ultimately work after attaching the virtio ISO and installing the drivers by hand, however, note of caution that the 126 release of virtio drivers did not work for me. Version 102 does. This is still work in progress from my perspective.=E2=80=8B
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALmWkDY9QdWOQJLUb3nu-7HS5DtXb5b8AANaAN0ZW92EH71ZnA>