Date: Wed, 2 Nov 2016 19:47:52 -0600 From: The Doctor <doctor@doctor.nl2k.ab.ca> To: Matt Churchyard <matt.churchyard@userve.net> Cc: Daniel Tihanyi <daniel.tihanyi@tetragir.com>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Windows 2016 Message-ID: <20161103014752.GA54371@doctor.nl2k.ab.ca> In-Reply-To: <20161101210419.GA55104@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <ec0716c52aeb4ea18d09b193ac61b493@SERVER.ad.usd-group.com> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> <cd71fc6fd0cb43a9adaa33c37cb95386@SERVER.ad.usd-group.com> <CALmWkDZJX-SN1EAp-buA3dgUX%2Bo8X7ZOt16qY4e8OaUaW4=4rQ@mail.gmail.com> <c5adf717ccca43d0a57757f4ca9003ea@SERVER.ad.usd-group.com> <20161101183420.GA38570@doctor.nl2k.ab.ca> <20161101210419.GA55104@doctor.nl2k.ab.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
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 +0000, Matt Churchyard wrote: > > > On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualization <freebsd-virtualization@freebsd.org<mailto: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 +0000, 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<http://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<http://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!!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161103014752.GA54371>