Date: Fri, 27 May 2016 20:03:50 +0300 From: Roman Bogorodskiy <novel@FreeBSD.org> To: Peter Grehan <grehan@freebsd.org> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: bhyve graphics support Message-ID: <20160527170347.GA25472@kloomba> In-Reply-To: <442c6d8f-2b64-c88b-382a-cf73eb6f7404@freebsd.org> References: <442c6d8f-2b64-c88b-382a-cf73eb6f7404@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Peter Grehan wrote: > As of r300829, support for graphic output has been checked into the=20 > projects/bhyve_graphics branch. This is just the usr.sbin/bhyve=20 > executable, so is quick and easy to build from source. >=20 > Assuming a reasonably current source tree is in /usr/src, > svn co http://svn.freebsd.org/base/projects/bhyve_graphics path/to/dir > cd path/to/dir > make BHYVE_SYSDIR=3D/usr/src -m /usr/src/share/mk >=20 > UEFI GOP support has been checked into the freebsd/edk2 repo: > =20 > https://github.com/freebsd/uefi-edk2/commit/a36132939e259df79b16699c03c6f= 1d63c7454b9 >=20 > A pre-built bhyve/UEFI binary image with GOP support is available at: > https://people.freebsd.org/~grehan/bhyve_uefi/BHYVE_UEFI_20160526.fd >=20 > The new bhyve executable supports some new devices. An example of using= =20 > them for Windows10 is: >=20 > bhyve \ > -c 2 \ > -s 3,ahci-cd,/images/win10_install.iso \ > -s 4,ahci-hd,/images/win10.img \ > -s 11,fbuf,tcp=3D0.0.0.0:5900,w=3D1600,h=3D900,wait \ > -s 20,xhci,tablet \ > -s 31,lpc \ > -l bootrom,/images/BHYVE_UEFI_20160526.fd \ > -m 2G -H -w \ > windows This is really great, thanks a lot to everyone who helped that happen! I've just tried to do a Fedora installation and it worked like a charm. A couple of questions: * There was a limitation that AHCI devices must use slots 3-6. [1] Is it still there? If yes, any plans to get rid of it? * It *seems* that now it's OK to cycle a VM this way: host# bhyve ... guest# reboot # guest goes away host# bhyve ... # run it again Previously (with bhyveload) it didn't work (for me at least) without doing "bhyvectl --destroy". Is it safe now not to call "bhyvectl --destroy" before the second run now? Thanks again, really glad to see this feature :-) 1: https://wiki.freebsd.org/bhyve/Windows Roman Bogorodskiy --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJXSH3zAAoJEMltX/4IwiJqF1QH/RqJfYL+aLdWSCWCjyiKjkRu 74RAo4I+fpzftRgB5jpd93mi4mS54/C8aM001Gf/+tDU7u1d3jD8FHopnWKQXkj4 M/zmTxeXdVG49nUbmp8Rgcaa3zWr/qddNyZB1o1XgurGe3Q5YIWc7nUiX07iRQ/+ CqkXQwGnX3xrU88gKSTESSax5dhNz+T+sLJYyDfcjFQrT61eklTbKw7xx5UvXBhK P5eS+sCcIMFeKKkdWEHfavdqtp/9Teop63Q+Hg5n2pRU3Gtlfy3nC4NwRHW48zl1 +sK4BMV31MEBTd39aWwvj9D02WactQVusGKpzKfjmIa26/R002F1F+PbQ9wWc2Y= =MXgX -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160527170347.GA25472>