From owner-freebsd-virtualization@freebsd.org Tue Oct 25 09:21:06 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B452C20D4E for ; Tue, 25 Oct 2016 09:21:06 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-outbound.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E3FE918F for ; Tue, 25 Oct 2016 09:21:05 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) by smtp-outbound.userve.net (8.15.1/8.15.1) with ESMTPS id u9P9KYDC072706 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 25 Oct 2016 10:20:35 +0100 (BST) (envelope-from matt.churchyard@userve.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1477387238; bh=7zqjHO2fOPRN9/6Wj5qdrz9j/z3NJH4aBdRSkmTpOAY=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=W8HHIBY8EaokY1ckmWRDf0W0bu2Iq8nHnW6dtT2R6SIPpbsAisrtdXaV3qguW1nBc 6riC8BAo8L8p6PIVEdAz8CnsW1bQ7+O4WidaH29wXDCvI9su/UXFQBq+KNI3wZkH3z bM57zDBwJ0RJ1zBC8hBUstG/YwAPbXN1XfbwkgVw= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 25 Oct 2016 10:20:29 +0100 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Tue, 25 Oct 2016 10:20:28 +0100 From: Matt Churchyard To: The Doctor CC: "freebsd-virtualization@freebsd.org" Subject: RE: Windows 2016 Server Thread-Topic: Windows 2016 Server Thread-Index: AQHSK8mJ2CakZ/g7jE+UHq0K36TtoaCzMrAAgAA2xwCAAAEMAIAAALUAgAPXOSCAAWEcgIAARA4w Date: Tue, 25 Oct 2016 09:20:28 +0000 Message-ID: <4cec0d5457ca45e1b2dee0b92055a439@SERVER.ad.usd-group.com> References: <20161021183120.GA21232@doctor.nl2k.ab.ca> <20161021190122.GA30602@doctor.nl2k.ab.ca> <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> In-Reply-To: <20161025060637.GA20650@doctor.nl2k.ab.ca> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2016 09:21:06 -0000 >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=20 > > >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is=20 > > >> invalid.] > > > > > > Something is wrong with your autounattend.xml file. > >=20 > > Still working on the 2k16 unattend file. Unfortunately things have=20 > > changed from TP5 in a non-obvious way :( > >=20 > > A workaround is to do a GUI install. > >=20 > > later, > >=20 > > Peter. >=20 > > Please explain what you mean by a GUI install. >=20 > Not sure if anyone's replied directly to you - >=20 > 1) Make sure you are running at least 11-RELEASE >=20 > 2) Use an "off-the-shelf" Windows install CD >=20 > 3) Add the following to your bhyve command >=20 > -s 29,fbuf,tcp=3D0.0.0.0:5900,w=3D800,h=3D600,wait > -s 30,xhci,tablet >=20 > 4) Run bhyve and then use a VNC client to connect and install using=20 > 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 o= n 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 add= ress of the bhyve host using VNC to view the "physical" guest console and w= atch 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 devi= ce by default. The easiest way to get this working is to boot the guest wi= th 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 lik= e iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve commands for y= ou. Matt