Re: Windows 2016

[The Doctor]

On Tue, Nov 01, 2016 at 12:34:20PM -0600, The Doctor wrote:
> On Tue, Nov 01, 2016 at 03:21:45PM +, Matt Churchyard wrote:
> > On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualization 
> > >
> >  wrote:
> > On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote:
> > > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote:
> > > > On Tue, Nov 01, 2016 at 09:02:57AM +, 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.
> > 
> > >All right, let me repeat what I am up aginst.
> > 
> > >I do set the IP configuration in the virtual BIOS.
> > 
> > >However when the Win2016 VM boots it sees
> > 
> > >1) the localhost
> > 
> > >2) its assigned IP address
> > 
> > >3) A yellow triangle where the ethernet adaptor is.
> > I'm not sure what people find so difficult about this - Just treat it like 
> > it was a real Windows machine
> > 
> > 1) Do not assign the guest's IP address on the host
> > 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean by 
> > this)
> > 
> > As you have found, the virtio-net network adapter has a yellow triangle in 
> > Windows, because it is not installed. You need to run bhyve but replace the 
> > Windows ISO with the virtio-net driver ISO, which you can download off the 
> > Internet; Then install the network driver through VNC. The guest has a 
> > "virtio-net" interface which is created by bhyve - This has nothing to do 
> > with your motherboard and you do not need to install any of the motherboard 
> > or physical interface drivers in the guest.
> 
> I have virtio-win-0.1.96.iso  in the .iso section.
> 
> Use that instead of the null-install.iso 
> ??

That did it!!

Couple of issues.

RDP the rules might have changed, have to check.

Hyper-V will not install.

What 

ubuntu 14.04 guest problem on freebsd 10 host

[tech-lists]

Hello list,

I have a number of ubuntu guests on this freebsd host, and I start them 
more or less the same way, but with one of them, the login prompt never 
arrives. To restart, I do this:


1. (each of them runs in screen, so I resume the screen, and from 
elsewhere, I log in via ssh and run shutdown -r now as root. So in the 
screen now, the vm has exited and I'm now at the freebsd server prompt.)


2. bhyvectl --destroy --vm=ubuntu0

3. grub-bhyve -m device.map -r hd0,msdos1 -M 4096M ubuntu0

4. bhyve -AI -H -P -s 0:0,hostbridge -s 1:0,lpc -s 2:0,virtio-net,tap3 
-s 3:0,virtio-blk,./ubuntu0.img -l com1,stdio -c 2 -m 4096M ubuntu0


The VM gets as far as this:

 * Starting web server apache2 [OK]
 * Starting authentication failure monitor fail2ban [ OK ]

...and nothing else. web everything in the vm is working. I'm just not 
getting the login prompt.


How can I fix this?

Also is there a way of taking the VM image, mounting it on some 
mountpoint on the freebsd host and directly editing the files within it?


Alternatively, is there a way of making grub boot the image into 
single-user-mode like one can with freebsd?


Many thanks,
--
J.
___
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"

Re: Windows 2016

[The Doctor]

On Tue, Nov 01, 2016 at 03:21:45PM +, Matt Churchyard wrote:
> On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualization 
> >
>  wrote:
> On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote:
> > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote:
> > > On Tue, Nov 01, 2016 at 09:02:57AM +, 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.
> 
> >All right, let me repeat what I am up aginst.
> 
> >I do set the IP configuration in the virtual BIOS.
> 
> >However when the Win2016 VM boots it sees
> 
> >1) the localhost
> 
> >2) its assigned IP address
> 
> >3) A yellow triangle where the ethernet adaptor is.
> I'm not sure what people find so difficult about this - Just treat it like it 
> was a real Windows machine
> 
> 1) Do not assign the guest's IP address on the host
> 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean by 
> this)
> 
> As you have found, the virtio-net network adapter has a yellow triangle in 
> Windows, because it is not installed. You need to run bhyve but replace the 
> Windows ISO with the virtio-net driver ISO, which you can download off the 
> Internet; Then install the network driver through VNC. The guest has a 
> "virtio-net" interface which is created by bhyve - This has nothing to do 
> with your motherboard and you do not need to install any of the motherboard 
> or physical interface drivers in the guest.

I have virtio-win-0.1.96.iso  in the .iso section.

Use that instead of the null-install.iso 
??

> 
> Once you have the virtio driver installed, you will have a "Redhat VirtIO" 
> network adapter in Windows, and you can assign an IP/Netmask/Gateway to this 
> just as you normally would in Windows.
> 
> Forget about the Linux machines. They have the virtio-net driver built in, so 
> you can just configure eth0 out-of-the-box like normal. If you've configured 
> their IP addresses on the bhyve host then that's not 

Re: Windows 2016

[The Doctor]

On Tue, Nov 01, 2016 at 03:35:37PM +0100, Daniel Tihanyi wrote:
> On Tue, 2016-11-01 at 08:22 -0600, The Doctor wrote:
> > On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote:
> > > 
> > > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote:
> > > > 
> > > > On Tue, Nov 01, 2016 at 09:02:57AM +, 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.
> > All right, let me repeat what I am up aginst.
> > 
> > I do set the IP configuration in the virtual BIOS.
> > 
> > However when the Win2016 VM boots it sees
> > 
> > 1) the localhost
> > 
> > 2) its assigned IP address
> > 
> > 3) A yellow triangle where the ethernet adaptor is.
> > 
> > 
> I don't really understand, what do you mean by virtual BIOS. If you
> boot up Windows, configure the IP Address, etc from there. Follow this
> guide to do so:?https://ittutorials.net/microsoft/windows-server-2016/s
> et-windows-server-2016-with-a-static-ip-address/

I guess you missed point 3), there is a yellow triangle 
where the ethernet adapter is.

Hence that I T Tutorial will not work.

I need to find a mtheod to get the Ethernet connection to work properly.

> ___
> 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"

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! 
http://www.fullyfollow.me/rootnl2k  Look at Psalms 14 and 53 on Atheism
Time for the USA to hold a referendum on its republic and vote to dissolve!! 

Re: Windows 2016

[Randy Terbush]

On Tue, Nov 1, 2016 at 11:24 AM, Randy Terbush  wrote:

> On Tue, Nov 1, 2016 at 9:21 AM, Matt Churchyard <
> matt.churchy...@userve.net> wrote:
>
>> On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via
>> freebsd-virtualization  wrote:
>>
>> On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote:
>> > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote:
>> > > On Tue, Nov 01, 2016 at 09:02:57AM +, 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.
>>
>> >All right, let me repeat what I am up aginst.
>>
>> >I do set the IP configuration in the virtual BIOS.
>>
>> >However when the Win2016 VM boots it sees
>>
>> >1) the localhost
>>
>> >2) its assigned IP address
>>
>> >3) A yellow triangle where the ethernet adaptor is.
>>
>> I'm not sure what people find so difficult about this - Just treat it
>> like it was a real Windows machine
>>
>> 1) Do not assign the guest's IP address on the host
>> 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean
>> by this)
>>
>> As you have found, the virtio-net network adapter has a yellow triangle
>> in Windows, because it is not installed. You need to run bhyve but replace
>> the Windows ISO with the virtio-net driver ISO, which you can download off
>> the Internet; Then install the network driver through VNC. The guest has a
>> "virtio-net" interface which is created by bhyve - This has nothing to do
>> with your motherboard and you do not need to install any of the motherboard
>> or physical interface drivers in the guest.
>>
>> Once you have the virtio driver installed, you will have a "Redhat
>> VirtIO" network adapter in Windows, and you can assign an
>> IP/Netmask/Gateway to this just as you normally would in Windows.
>>
>> Forget about the Linux machines. They have the virtio-net driver built
>> in, so you can just configure eth0 out-of-the-box like normal. If you've
>> configured their IP addresses on the bhyve host then that's not 

Re: Windows 2016

[Randy Terbush]

On Tue, Nov 1, 2016 at 9:21 AM, Matt Churchyard 
wrote:

> On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualization
>  wrote:
>
> On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote:
> > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote:
> > > On Tue, Nov 01, 2016 at 09:02:57AM +, 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.
>
> >All right, let me repeat what I am up aginst.
>
> >I do set the IP configuration in the virtual BIOS.
>
> >However when the Win2016 VM boots it sees
>
> >1) the localhost
>
> >2) its assigned IP address
>
> >3) A yellow triangle where the ethernet adaptor is.
>
> I'm not sure what people find so difficult about this - Just treat it like
> it was a real Windows machine
>
> 1) Do not assign the guest's IP address on the host
> 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean by
> this)
>
> As you have found, the virtio-net network adapter has a yellow triangle in
> Windows, because it is not installed. You need to run bhyve but replace the
> Windows ISO with the virtio-net driver ISO, which you can download off the
> Internet; Then install the network driver through VNC. The guest has a
> "virtio-net" interface which is created by bhyve - This has nothing to do
> with your motherboard and you do not need to install any of the motherboard
> or physical interface drivers in the guest.
>
> Once you have the virtio driver installed, you will have a "Redhat VirtIO"
> network adapter in Windows, and you can assign an IP/Netmask/Gateway to
> this just as you normally would in Windows.
>
> Forget about the Linux machines. They have the virtio-net driver built in,
> so you can just configure eth0 out-of-the-box like normal. If you've
> configured their IP addresses on the bhyve host then that's not really the
> correct way to configure things, even if it doesn't actually break
> anything; The IP address should be configured inside the guest OS.
>
> Matt
>
>
>
>
>
> ​>Can you guys confirm that you 

RE: Windows 2016

[Matt Churchyard via freebsd-virtualization]

On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualization 
> 
wrote:
On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote:
> On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote:
> > On Tue, Nov 01, 2016 at 09:02:57AM +, 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.

>All right, let me repeat what I am up aginst.

>I do set the IP configuration in the virtual BIOS.

>However when the Win2016 VM boots it sees

>1) the localhost

>2) its assigned IP address

>3) A yellow triangle where the ethernet adaptor is.
I'm not sure what people find so difficult about this - Just treat it like it 
was a real Windows machine

1) Do not assign the guest's IP address on the host
2) Do not set the IP in the guest BIOS (I'm not even sure what you mean by this)

As you have found, the virtio-net network adapter has a yellow triangle in 
Windows, because it is not installed. You need to run bhyve but replace the 
Windows ISO with the virtio-net driver ISO, which you can download off the 
Internet; Then install the network driver through VNC. The guest has a 
"virtio-net" interface which is created by bhyve - This has nothing to do with 
your motherboard and you do not need to install any of the motherboard or 
physical interface drivers in the guest.

Once you have the virtio driver installed, you will have a "Redhat VirtIO" 
network adapter in Windows, and you can assign an IP/Netmask/Gateway to this 
just as you normally would in Windows.

Forget about the Linux machines. They have the virtio-net driver built in, so 
you can just configure eth0 out-of-the-box like normal. If you've configured 
their IP addresses on the bhyve host then that's not really the correct way to 
configure things, even if it doesn't actually break anything; The IP address 
should be configured inside the guest OS.

Matt


​>Can you guys confirm that you actually have a Windows 2016 vm running?

>As I have said, I have installed nearly every version of Windows OS vms with 
>Bhyve (vm-bhyve) successfully with the >exception of Windows 2016.

>DHCP does not work. Assigning an 

Re: Windows 2016

[Randy Terbush]

On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualization <
freebsd-virtualization@freebsd.org> wrote:

> On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote:
> > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote:
> > > On Tue, Nov 01, 2016 at 09:02:57AM +, 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.
>
> >All right, let me repeat what I am up aginst.
>
> >I do set the IP configuration in the virtual BIOS.
>
> >However when the Win2016 VM boots it sees
>
> >1) the localhost
>
> >2) its assigned IP address
>
> >3) A yellow triangle where the ethernet adaptor is.
>
> I'm not sure what people find so difficult about this - Just treat it like
> it was a real Windows machine
>
> 1) Do not assign the guest's IP address on the host
> 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean by
> this)
>
> As you have found, the virtio-net network adapter has a yellow triangle in
> Windows, because it is not installed. You need to run bhyve but replace the
> Windows ISO with the virtio-net driver ISO, which you can download off the
> Internet; Then install the network driver through VNC. The guest has a
> "virtio-net" interface which is created by bhyve - This has nothing to do
> with your motherboard and you do not need to install any of the motherboard
> or physical interface drivers in the guest.
>
> Once you have the virtio driver installed, you will have a "Redhat VirtIO"
> network adapter in Windows, and you can assign an IP/Netmask/Gateway to
> this just as you normally would in Windows.
>
> Forget about the Linux machines. They have the virtio-net driver built in,
> so you can just configure eth0 out-of-the-box like normal. If you've
> configured their IP addresses on the bhyve host then that's not really the
> correct way to configure things, even if it doesn't actually break
> anything; The IP address should be configured inside the guest OS.
>
> Matt
>
>
​Can you guys confirm that you actually have a Windows 2016 vm running?

As I have said, I have installed nearly every version of 

RE: Windows 2016

[Matt Churchyard via freebsd-virtualization]

On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote:
> On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote:
> > On Tue, Nov 01, 2016 at 09:02:57AM +, 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.

>All right, let me repeat what I am up aginst.

>I do set the IP configuration in the virtual BIOS.

>However when the Win2016 VM boots it sees

>1) the localhost

>2) its assigned IP address

>3) A yellow triangle where the ethernet adaptor is.

I'm not sure what people find so difficult about this - Just treat it like it 
was a real Windows machine

1) Do not assign the guest's IP address on the host
2) Do not set the IP in the guest BIOS (I'm not even sure what you mean by this)

As you have found, the virtio-net network adapter has a yellow triangle in 
Windows, because it is not installed. You need to run bhyve but replace the 
Windows ISO with the virtio-net driver ISO, which you can download off the 
Internet; Then install the network driver through VNC. The guest has a 
"virtio-net" interface which is created by bhyve - This has nothing to do with 
your motherboard and you do not need to install any of the motherboard or 
physical interface drivers in the guest.

Once you have the virtio driver installed, you will have a "Redhat VirtIO" 
network adapter in Windows, and you can assign an IP/Netmask/Gateway to this 
just as you normally would in Windows.

Forget about the Linux machines. They have the virtio-net driver built in, so 
you can just configure eth0 out-of-the-box like normal. If you've configured 
their IP addresses on the bhyve host then that's not really the correct way to 
configure things, even if it doesn't actually break anything; The IP address 
should be configured inside the guest OS.

Matt
___
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"

Re: Windows 2016

[Daniel Tihanyi]

On Tue, 2016-11-01 at 08:22 -0600, The Doctor wrote:
> On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote:
> > 
> > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote:
> > > 
> > > On Tue, Nov 01, 2016 at 09:02:57AM +, 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.
> All right, let me repeat what I am up aginst.
> 
> I do set the IP configuration in the virtual BIOS.
> 
> However when the Win2016 VM boots it sees
> 
> 1) the localhost
> 
> 2) its assigned IP address
> 
> 3) A yellow triangle where the ethernet adaptor is.
> 
> 
I don't really understand, what do you mean by virtual BIOS. If you
boot up Windows, configure the IP Address, etc from there. Follow this
guide to do so: https://ittutorials.net/microsoft/windows-server-2016/s
et-windows-server-2016-with-a-static-ip-address/
___
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"

Re: Windows 2016

[The Doctor]

On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote:
> On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote:
> > On Tue, Nov 01, 2016 at 09:02:57AM +, 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.

All right, let me repeat what I am up aginst.

I do set the IP configuration in the virtual BIOS.

However when the Win2016 VM boots it sees

1) the localhost

2) its assigned IP address

3) A yellow triangle where the ethernet adaptor is.

> ___
> 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"

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! 
http://www.fullyfollow.me/rootnl2k  Look at Psalms 14 and 53 on Atheism
Time for the USA to hold a referendum on its republic and vote to dissolve!! 
___
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"

Re: Windows 2016

[The Doctor]

On Tue, Nov 01, 2016 at 08:14:49AM +, Daniel Tihanyi wrote:
> Hi,
> 
> first of all, could you please clarify if you use VirtualBox, bhyve or
> any other virtualization platform?
> Additionally, could you please share, how did you configured your
> network for the VMs?
> What do you use for DHCP Server? Is it configured properly?
> Thank you very much!
>

It is bhyve and I do not use DHCP.

Please NEVER top post!

> --
> Daniel Tihanyi
> 
> On Tue, Nov 1, 2016, at 04:45, The Doctor 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.
> > 
> > What must I do to convince this box that is it on a switch
> > 
> > 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.
> > 
> > -- 
> > Member - Liberal International This is doctor@@nl2k.ab.ca Ici
> > doctor@@nl2k.ab.ca
> > God,Queen and country!Never Satan President Republic!Beware AntiChrist
> > rising! 
> > http://www.fullyfollow.me/rootnl2k  Look at Psalms 14 and 53 on Atheism
> > Time for the USA to hold a referendum on its republic and vote to
> > dissolve!! 
> > ___
> > 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"
> ___
> 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"

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! 
http://www.fullyfollow.me/rootnl2k  Look at Psalms 14 and 53 on Atheism
Time for the USA to hold a referendum on its republic and vote to dissolve!! 
___
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"

RE: Windows 2016

[Matt Churchyard via freebsd-virtualization]

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

RE: Windows 2016

[Matt Churchyard via freebsd-virtualization]

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

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"

Re: Windows 2016

[Daniel Tihanyi]

Hi,

first of all, could you please clarify if you use VirtualBox, bhyve or
any other virtualization platform?
Additionally, could you please share, how did you configured your
network for the VMs?
What do you use for DHCP Server? Is it configured properly?
Thank you very much!

--
Daniel Tihanyi

On Tue, Nov 1, 2016, at 04:45, The Doctor 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.
> 
> What must I do to convince this box that is it on a switch
> 
> 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.
> 
> -- 
> Member - Liberal International This is doctor@@nl2k.ab.ca Ici
> doctor@@nl2k.ab.ca
> God,Queen and country!Never Satan President Republic!Beware AntiChrist
> rising! 
> http://www.fullyfollow.me/rootnl2k  Look at Psalms 14 and 53 on Atheism
> Time for the USA to hold a referendum on its republic and vote to
> dissolve!! 
> ___
> 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"
___
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"