From owner-freebsd-virtualization@freebsd.org Mon May 30 07:25:34 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 47B1EB5486D for ; Mon, 30 May 2016 07:25:34 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from mail1.yamagi.org (yugo.yamagi.org [212.48.122.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0F8A91FFD; Mon, 30 May 2016 07:25:33 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from [192.168.100.101] (helo=aka) by mail1.yamagi.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.86 (FreeBSD)) (envelope-from ) id 1b7HZG-0001tS-Nc; Mon, 30 May 2016 09:25:25 +0200 Date: Mon, 30 May 2016 09:24:49 +0200 From: Yamagi Burmeister To: grehan@freebsd.org Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve graphics support Message-Id: <20160530092449.399f5c4f315d12e1144b49b8@yamagi.org> In-Reply-To: <1fb4af03-1131-011b-faf7-fa993862c2fa@freebsd.org> References: <442c6d8f-2b64-c88b-382a-cf73eb6f7404@freebsd.org> <20160527104405.GA15808@e-new.0x20.net> <20160527115540.GB15808@e-new.0x20.net> <20160527141557.e2ee91ee437a3893f818c468@yamagi.org> <1fb4af03-1131-011b-faf7-fa993862c2fa@freebsd.org> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 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: Mon, 30 May 2016 07:25:34 -0000 Hello, > > As far as I know UEFI supports ahci-* boot devices only. For the basic > > UEFI support without GOP the AHCI devices needed to be mapped on slot 3 > > and 4. I don't know if that's still the case. >=20 > Depends on the o/s being booted - if it needs legacy interrupt=20 > support, the only available slots with routing set up are 3/4/5/6. >=20 > UEFI operates in polled-mode so it has no constraints on it's own. Ah okay. That's good to know. At least for the Windows 2016 case. > > I've got working VNC access to a FreeBSD 10.3 VM. My Windows 7 install > > disc starts up, but the mouse is not working. Keystrokes through VNC > > give "atkbd data buffer full" errors. I'll open a new thread for that > > if I can't figure it out. >=20 > XHCI isn't in Windows7 so you can just remove that config line,=20 > pushing mouse input through the PS2 mouse. That was a little bit strange, it seemed like the emulated ps/2 devices just wouldn't work on a Win 7 VM. The "atkbd data buffer full" may be an indication for not delivered interrupts or something like that. After I've rebooted the host things suddenly started to work. Maybe some kind of system inconsistency. It was some 11-CURRENT with about 4 weeks uptime. It may be a good idea to add a note to the Windows installation guide at https://people.freebsd.org/~grehan/bhyve_uefi/windows_install.txt that Window 7 requieres AHCI disks with a blocksize if 512 bytes. Otherwise the installation will fail with "Windows Setup could not configure Windows on this computer?s hardware" and Windows Update will bail out with error 0xc8000247. Regards, Yamagi --=20 Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB