>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 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.

--------------------------------------------
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.
--------------------------------------------

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.
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Reply via email to