Date: Fri, 27 May 2016 08:11:35 -0700 From: Peter Grehan <grehan@freebsd.org> To: Yamagi Burmeister <lists@yamagi.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve graphics support Message-ID: <1fb4af03-1131-011b-faf7-fa993862c2fa@freebsd.org> In-Reply-To: <20160527141557.e2ee91ee437a3893f818c468@yamagi.org> References: <442c6d8f-2b64-c88b-382a-cf73eb6f7404@freebsd.org> <20160527104405.GA15808@e-new.0x20.net> <CACLnyCJ0utuCX==f%2BA9ys=fi4R5kGCY4GbDBmuWBwKYXRyAq8Q@mail.gmail.com> <20160527115540.GB15808@e-new.0x20.net> <20160527141557.e2ee91ee437a3893f818c468@yamagi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Yamagi, > 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. Depends on the o/s being booted - if it needs legacy interrupt support, the only available slots with routing set up are 3/4/5/6. UEFI operates in polled-mode so it has no constraints on it's own. > 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. XHCI isn't in Windows7 so you can just remove that config line, pushing mouse input through the PS2 mouse. later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1fb4af03-1131-011b-faf7-fa993862c2fa>