Date: Tue, 25 Oct 2016 09:20:28 +0000 From: Matt Churchyard <matt.churchyard@userve.net> To: The Doctor <doctor@doctor.nl2k.ab.ca> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: RE: Windows 2016 Server Message-ID: <4cec0d5457ca45e1b2dee0b92055a439@SERVER.ad.usd-group.com> In-Reply-To: <20161025060637.GA20650@doctor.nl2k.ab.ca> References: <20161021183120.GA21232@doctor.nl2k.ab.ca> <20161021190122.GA30602@doctor.nl2k.ab.ca> <alpine.BSF.2.20.1610212216310.22551@z.fncre.vasb> <0406d06f-aa1a-677c-775a-b09a3ebd3073@freebsd.org> <20161021222342.GA80184@doctor.nl2k.ab.ca> <33e8e02d845145918591d25196402491@SERVER.ad.usd-group.com> <20161025060637.GA20650@doctor.nl2k.ab.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
>On Mon, Oct 24, 2016 at 08:07:13AM +0000, 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4cec0d5457ca45e1b2dee0b92055a439>