Re: Windows 2016

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

Re: Windows 2016

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

Re: Windows 2016

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

Re: Windows 2016

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

Re: Windows 2016

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

Re: Windows 2016

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

Re: Windows 2016

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

Re: Windows 2016

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

Re: Windows 2016

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

RE: Windows 2016

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

Re: Windows 2016

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

RE: Windows 2016

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

Re: Windows 2016

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

Re: Windows 2016

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

Re: Windows 2016

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

RE: Windows 2016

>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

RE: Windows 2016

>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

Re: Windows 2016

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

Re: Windows 2016 Server

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

Re: Windows 2016 Server

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

Re: Windows 2016 Server

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 >

Re: Windows 2016 Server

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]

RE: Windows 2016 Server

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

Re: Windows 2016 Server

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

RE: Windows 2016 Server

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

Re: Windows 2016 Server

[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 :(

Re: Windows 2016 Server

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 >