Re: Windows 2016

2016-11-03 Thread The Doctor
On Wed, Nov 02, 2016 at 09:28:59PM -0600, The Doctor wrote:
> On Wed, Nov 02, 2016 at 07:00:08PM -0700, Peter Grehan wrote:
> > Hi,
> > 
> > > So the question is how do I pass to Windows 2016 that the CPU it is using
> > > is a CPU capable of Hyper-V ?
> > 
> >   That requires nested hypervisor support, which isn't yet in bhyve.
> >
> 
> So what would it take for bhyve to programme in nested hypervisor support?

I just noted that my CPUs are Intel Xeon 2603v4 .

Is it possible to do a passthru instead of programming bhyve to do a nested 
hypervisor?

> 
> > later,
> > 
> > Peter.
> > 
> 
> -- 
> 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"

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

2016-11-02 Thread The Doctor
On Wed, Nov 02, 2016 at 07:00:08PM -0700, Peter Grehan wrote:
> Hi,
> 
> > So the question is how do I pass to Windows 2016 that the CPU it is using
> > is a CPU capable of Hyper-V ?
> 
>   That requires nested hypervisor support, which isn't yet in bhyve.
>

So what would it take for bhyve to programme in nested hypervisor support?

> later,
> 
> Peter.
> 

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

2016-11-02 Thread Peter Grehan

Hi,


So the question is how do I pass to Windows 2016 that the CPU it is using
is a CPU capable of Hyper-V ?


 That requires nested hypervisor support, which isn't yet in bhyve.

later,

Peter.

___
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

2016-11-02 Thread The Doctor
Yes you can get Windows 2016 to work on a FreeBSD VM 

Summary below with edits.

On Tue, Nov 01, 2016 at 03:04:19PM -0600, The Doctor wrote:
> 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:
> > > > > >
> > > > > > >
> > > > >
> > > > > /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/virtio-win-0.1.96.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 &

Please note I am running the from a /path/to/vm as root of all VMs.

> 
> That did it!!
> 
> Couple of issues.
> 
> RDP the rules might have changed, have to check.

Looking at this.

> 
> Hyper-V will not install.
> 
> What gives?
> 


So the question is how do I pass to Windows 2016 that the CPU it is using
is a CPU capable of Hyper-V ?

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

2016-11-01 Thread 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 

Re: Windows 2016

2016-11-01 Thread 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

2016-11-01 Thread 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

2016-11-01 Thread 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

2016-11-01 Thread 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

2016-11-01 Thread 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

2016-11-01 Thread 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

2016-11-01 Thread 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

2016-11-01 Thread 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

2016-11-01 Thread 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

2016-11-01 Thread 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

2016-11-01 Thread 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

2016-11-01 Thread 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

2016-11-01 Thread 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"


Re: Windows 2016 Server

2016-10-25 Thread Randy Terbush
--
Randy

On Tue, Oct 25, 2016 at 9:38 AM, Dave Shariff Yadallee - System
Administrator a.k.a. The Root of the Problem  wrote:

> On Tue, Oct 25, 2016 at 08:33:47AM -0600, Randy Terbush wrote:
> > On Tue, Oct 25, 2016 at 7:58 AM, The Doctor 
> > wrote:
> >
> > > On Tue, Oct 25, 2016 at 09:20:28AM +, Matt Churchyard wrote:
> > >
> > > > One other issue is that Windows doesn't support the virtio-net
> network
> > > device by default.  The easiest way to get this working is to boot the
> > > guest with the virtio driver ISO attached instead of the Windows
> install
> > > disk (once Windows is installed and working). You can then install the
> > > driver for the network interface from the CD using the VNC console.
> > > >
> > > > Depending on what you are doing you may find it easier to use
> something
> > > like iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve
> commands
> > > for you.
> > > >
> > > > Matt
> > >
> > > I will look into the iohyve , saw that last night.
> > >
> > > Does this also apply to UEFU BSDs / Linuxes ?
> > >
> >
> > ???Just to chime in quickly on this thread... I am a big fan of
> vm-bhyve. It
> > has made it much easier to sort bhyve out in general and get through some
> > of these new options for supported guests.
> >
> > Regarding Linux and UEFI, much of this also applies there. I've
> > successfully installed a LinuxMint guest. I will offer that after the
> > install, the boot process hung at the EFI. After exiting from the Shell>
> > prompt that eventually appears, it is possible to navigate the UEFI bios
> > settings to pick a bootable device. Only after rerunning 'grub2-install'
> > was I able to have a Linux guest that would boot without fiddling.
> > ???
> Let me give you my setup.
>
> No Zpool here.
>
> I am running FreeBSD 11 UEFI on x86_64.
>
> I have set up some non-UEFI guest successfull ,
>
> Fedora, Centos and Ubuntu.
>
> If it the UEFI part using a non-zpool environment
>
> that I am trying to wrap my head around.
>
> Smilir to Windows, I did install Fedora using
> UEFI but then
> could not go to the
> second stage, i.e. booting into the VM.
>
> Hence I do need to understand how to this with my environment using
> purely bhyve.


​As mentioned, I'm using vm-bhyve to insulating me from the learning curve
of "pure bhyve". https://github.com/churchers/vm-bhyve

A few more details about my setup.

FreeBSD 11-stable (reguired for vnc graphics to work with UEFI guests)

Relevant installed packages:
vm-bhyve
bhyve-firmware
grub2-bhyve
uefi-edk2-bhyve
uefi-edk2-bhyve-csm

​While vm-bhyve is running in a zpool, the guests are using disk image
files.

The following template allowed me to install LinuxMint through graphic VNC
interface.

​guest="linux"
uefi="yes"
cpu=1
memory=2G
graphics="yes"
graphics_res="1600x1200"
graphics_wait="yes"
xhci_mouse="yes"
network0_type="virtio-net"
network0_switch="public"
disk0_type="virtio-blk"
disk0_name="disk0.img"
grub_run_partition="1"

​vm create -t mint -s 30G mint
vm install mint​ linuxmint-18-cinnamon-64bit.iso (32bit would not install
as a UEFI guest)
vm list (shows running bhyve guests and indicates the IP and port that VNC
is running on for this guest)
vncviewer 127.0.0.1:5900

Top-level listing of the vm zpool shows the layout which includes a
.template and .iso directory to collect your configs and install isos. Nice
clean setup.

[root: /vm]# ls -l
total 171
drwxr-xr-x  2 root  wheel   5 Jul 20 10:01 .config
drwxr-xr-x  2 root  wheel  10 Oct 24 12:10 .iso
drwxr-xr-x  2 root  wheel  17 Oct 24 11:56 .templates
drwxr-xr-x  2 root  wheel   8 Oct  3 21:41 kali
drwxr-xr-x  2 root  wheel   6 Oct  2 18:13 macos
drwxr-xr-x  2 root  wheel   8 Oct 25 05:37 mint
drwxr-xr-x  2 root  wheel   7 Oct 22 15:31 win2012
drwxr-xr-x  2 root  wheel   5 Oct 10 16:58 winapp

(NOTE: still trying to get a working MacOS guest running...)
___
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 Server

2016-10-25 Thread Dave Shariff Yadallee - System Administrator a.k.a. The Root of the Problem
On Tue, Oct 25, 2016 at 08:33:47AM -0600, Randy Terbush wrote:
> On Tue, Oct 25, 2016 at 7:58 AM, The Doctor 
> wrote:
> 
> > On Tue, Oct 25, 2016 at 09:20:28AM +, Matt Churchyard wrote:
> >
> > > One other issue is that Windows doesn't support the virtio-net network
> > device by default.  The easiest way to get this working is to boot the
> > guest with the virtio driver ISO attached instead of the Windows install
> > disk (once Windows is installed and working). You can then install the
> > driver for the network interface from the CD using the VNC console.
> > >
> > > Depending on what you are doing you may find it easier to use something
> > like iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve commands
> > for you.
> > >
> > > Matt
> >
> > I will look into the iohyve , saw that last night.
> >
> > Does this also apply to UEFU BSDs / Linuxes ?
> >
> 
> ???Just to chime in quickly on this thread... I am a big fan of vm-bhyve. It
> has made it much easier to sort bhyve out in general and get through some
> of these new options for supported guests.
> 
> Regarding Linux and UEFI, much of this also applies there. I've
> successfully installed a LinuxMint guest. I will offer that after the
> install, the boot process hung at the EFI. After exiting from the Shell>
> prompt that eventually appears, it is possible to navigate the UEFI bios
> settings to pick a bootable device. Only after rerunning 'grub2-install'
> was I able to have a Linux guest that would boot without fiddling.
> ???
Let me give you my setup.

No Zpool here.

I am running FreeBSD 11 UEFI on x86_64.

I have set up some non-UEFI guest successfull , 

Fedora, Centos and Ubuntu.

If it the UEFI part using a non-zpool environment 

that I am trying to wrap my head around.

Smilir to Windows, I did install Fedora using 
UEFI but then 
could not go to the 
second stage, i.e. booting into the VM.

Hence I do need to understand how to this with my environment using
purely bhyve.



-- 
For effective Internet Etiquette and communications read 
http://catb.org/jargon/html/T/top-post.html, http://idallen.com/topposting.html
& http://www.caliburn.nl/topposting.html
___
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 Server

2016-10-25 Thread Randy Terbush
On Tue, Oct 25, 2016 at 7:58 AM, The Doctor 
wrote:

> On Tue, Oct 25, 2016 at 09:20:28AM +, Matt Churchyard wrote:
>
> > One other issue is that Windows doesn't support the virtio-net network
> device by default.  The easiest way to get this working is to boot the
> guest with the virtio driver ISO attached instead of the Windows install
> disk (once Windows is installed and working). You can then install the
> driver for the network interface from the CD using the VNC console.
> >
> > Depending on what you are doing you may find it easier to use something
> like iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve commands
> for you.
> >
> > Matt
>
> I will look into the iohyve , saw that last night.
>
> Does this also apply to UEFU BSDs / Linuxes ?
>

​Just to chime in quickly on this thread... I am a big fan of vm-bhyve. It
has made it much easier to sort bhyve out in general and get through some
of these new options for supported guests.

Regarding Linux and UEFI, much of this also applies there. I've
successfully installed a LinuxMint guest. I will offer that after the
install, the boot process hung at the EFI. After exiting from the Shell>
prompt that eventually appears, it is possible to navigate the UEFI bios
settings to pick a bootable device. Only after rerunning 'grub2-install'
was I able to have a Linux guest that would boot without fiddling.
​
___
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 Server

2016-10-25 Thread The Doctor
On Tue, Oct 25, 2016 at 09:20:28AM +, Matt Churchyard wrote:
> >On Mon, Oct 24, 2016 at 08:07:13AM +, Matt Churchyard wrote:
> > On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote:
> > > >> [Windows could not parse or process unattend answer file 
> > > >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is 
> > > >> invalid.]
> > > >
> > > > Something is wrong with your autounattend.xml file.
> > > 
> > >   Still working on the 2k16 unattend file. Unfortunately things have 
> > > changed from TP5 in a non-obvious way :(
> > > 
> > >   A workaround is to do a GUI install.
> > > 
> > > later,
> > > 
> > > Peter.
> > 
> > > Please explain what you mean by a GUI install.
> > 
> > Not sure if anyone's replied directly to you -
> > 
> > 1) Make sure you are running at least 11-RELEASE
> > 
> > 2) Use an "off-the-shelf" Windows install CD
> > 
> > 3) Add the following to your bhyve command
> > 
> > -s 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait
> > -s 30,xhci,tablet
> > 
> > 4) Run bhyve and then use a VNC client to connect and install using 
> > the normal Windows GUI
> >
> 
> >Well all right did follow https://wiki.freebsd.org/bhyve/UEFI
> 
> 
> >My next question is after the initial install is done, how do I followup on 
> >the next step , i.e. to see if the VM is booting.
> 
> As long as you have the fbuf device specified you can connect to the IP 
> address of the bhyve host using VNC to view the "physical" guest console and 
> watch it boot. Usually with Windows you'd then use the VNC console to log in 
> and set up permanent RDP access.
> 
> One other issue is that Windows doesn't support the virtio-net network device 
> by default.  The easiest way to get this working is to boot the guest with 
> the virtio driver ISO attached instead of the Windows install disk (once 
> Windows is installed and working). You can then install the driver for the 
> network interface from the CD using the VNC console.
> 
> Depending on what you are doing you may find it easier to use something like 
> iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve commands for you.
> 
> Matt

I will look into the iohyve , saw that last night.

Does this also apply to UEFU BSDs / Linuxes ?

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

2016-10-25 Thread Matt Churchyard via freebsd-virtualization
>On Mon, Oct 24, 2016 at 08:07:13AM +, Matt Churchyard wrote:
> On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote:
> > >> [Windows could not parse or process unattend answer file 
> > >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is 
> > >> invalid.]
> > >
> > > Something is wrong with your autounattend.xml file.
> > 
> >   Still working on the 2k16 unattend file. Unfortunately things have 
> > changed from TP5 in a non-obvious way :(
> > 
> >   A workaround is to do a GUI install.
> > 
> > later,
> > 
> > Peter.
> 
> > Please explain what you mean by a GUI install.
> 
> Not sure if anyone's replied directly to you -
> 
> 1) Make sure you are running at least 11-RELEASE
> 
> 2) Use an "off-the-shelf" Windows install CD
> 
> 3) Add the following to your bhyve command
> 
> -s 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait
> -s 30,xhci,tablet
> 
> 4) Run bhyve and then use a VNC client to connect and install using 
> the normal Windows GUI
>

>Well all right did follow https://wiki.freebsd.org/bhyve/UEFI


>My next question is after the initial install is done, how do I followup on 
>the next step , i.e. to see if the VM is booting.

As long as you have the fbuf device specified you can connect to the IP address 
of the bhyve host using VNC to view the "physical" guest console and watch it 
boot. Usually with Windows you'd then use the VNC console to log in and set up 
permanent RDP access.

One other issue is that Windows doesn't support the virtio-net network device 
by default.  The easiest way to get this working is to boot the guest with the 
virtio driver ISO attached instead of the Windows install disk (once Windows is 
installed and working). You can then install the driver for the network 
interface from the CD using the VNC console.

Depending on what you are doing you may find it easier to use something like 
iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve commands for you.

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 Server

2016-10-25 Thread The Doctor
On Mon, Oct 24, 2016 at 08:07:13AM +, Matt Churchyard wrote:
> On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote:
> > >> [Windows could not parse or process unattend answer file 
> > >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is 
> > >> invalid.]
> > >
> > > Something is wrong with your autounattend.xml file.
> > 
> >   Still working on the 2k16 unattend file. Unfortunately things have 
> > changed from TP5 in a non-obvious way :(
> > 
> >   A workaround is to do a GUI install.
> > 
> > later,
> > 
> > Peter.
> 
> > Please explain what you mean by a GUI install.
> 
> Not sure if anyone's replied directly to you -
> 
> 1) Make sure you are running at least 11-RELEASE
> 
> 2) Use an "off-the-shelf" Windows install CD
> 
> 3) Add the following to your bhyve command
> 
> -s 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait
> -s 30,xhci,tablet
> 
> 4) Run bhyve and then use a VNC client to connect and install using the 
> normal Windows GUI
>

Well all right did follow https://wiki.freebsd.org/bhyve/UEFI


My next question is after the initial install is done,
how do I followup on the next step , i.e. to see if the VM is booting.

> Matt

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

2016-10-24 Thread Matt Churchyard via freebsd-virtualization
On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote:
> >> [Windows could not parse or process unattend answer file 
> >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is 
> >> invalid.]
> >
> > Something is wrong with your autounattend.xml file.
> 
>   Still working on the 2k16 unattend file. Unfortunately things have 
> changed from TP5 in a non-obvious way :(
> 
>   A workaround is to do a GUI install.
> 
> later,
> 
> Peter.

> Please explain what you mean by a GUI install.

Not sure if anyone's replied directly to you -

1) Make sure you are running at least 11-RELEASE

2) Use an "off-the-shelf" Windows install CD

3) Add the following to your bhyve command

-s 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait
-s 30,xhci,tablet

4) Run bhyve and then use a VNC client to connect and install using the normal 
Windows GUI

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 Server

2016-10-21 Thread Peter Grehan

[Windows could not parse or process unattend answer file
[D:\autounattend.xml] for pass [windowsPE]. The answer file is
invalid.]


Something is wrong with your autounattend.xml file.


 Still working on the 2k16 unattend file. Unfortunately things have 
changed from TP5 in a non-obvious way :(


 A workaround is to do a GUI install.

later,

Peter.
___
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 Server

2016-10-21 Thread Marcin Cieslak
On Fri, 21 Oct 2016, The Doctor wrote:
>   What went wrong?

Windows:

> [Windows could not parse or process unattend answer file 
> [D:\autounattend.xml] for pass [windowsPE]. The answer file is invalid.]

Something is wrong with your autounattend.xml file.

Marcin
___
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 Server

2016-10-21 Thread The Doctor
On Fri, Oct 21, 2016 at 12:31:20PM -0600, The Doctor wrote:
> Does anyone have Windows 2016 Server Release 1 working on thier sysem.
> 
> After following https://wiki.freebsd.org/bhyve/Windows 
> 
> I run
> 
> /usr/sbin/bhyve -c 2 -s 0,hostbridge -s 3,ahci-hd,./windows2016.img -s 
> 4,ahci-cd,./.iso/win2k16install.iso -s 10,virtio-net,tap15 -s 31,lpc -l 
> com1,/dev/nmdm15A -l com2,/dev/nmdm16A -l 
> bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -m 2G -H -w 
> windows2016guest
> 
> I can cu -l into /dev/nmdm15B  I see SAC
> 
> but cannot seem to go further.
> 
> Help.

Further in one of the Windows, I see

= 0x0, hrValidated = 0x1, hrResult = 0x80220005
2016-10-21 12:58:10, Info  IBSUnattendErrorFromResults: Hit
 an unattend error; dumping any info we have about the failure...
 2016-10-21 12:58:10, Info  IBSUnattendDumpSetting: --Un
 attend setting error / warning--
 2016-10-21 12:58:10, Info  IBSUnattendDumpSetting: Error co
 de = 0x80220005
 2016-10-21 12:58:10, Info  IBSUnattendDumpSetting: Pass = w
 indowsPE
 2016-10-21 12:58:10, Info  IBSUnattendDumpSetting: 
 
 2016-10-21 12:58:10, Info  IBSUnattendErrorFromResults: Err
 or text = Windows could not parse or process unattend answer file [D:\autounatt
 end.xml] for pass [windowsPE]. The answer file is invalid.
 2016-10-21 12:58:10, Error  [0x0600c2] IBSCallback_Unattend_InitEngine:
 An error occurred while finding/loading the unattend file; hr = 0x1, hrResult =
  0x80220005[gle=0x0490]
  2016-10-21 12:58:10, Info  IBSLIB PublishCriticalError: 
Publish
  ing blocked message [Windows could not parse or process unattend answer file 
[D
  :\autounattend.xml] for pass [windowsPE]. The answer file is invalid.]
  2016-10-21 12:58:10, Info This installation is blocked
  from completing due to compliance failures or invalid input; this is not an 
int
  ernal error.


  What went wrong?

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