Peter Grehan wrote:

> As of r300829, support for graphic output has been checked into the 
> projects/bhyve_graphics branch. This is just the usr.sbin/bhyve 
> executable, so is quick and easy to build from source.
> 
> 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=/usr/src -m /usr/src/share/mk
> 
> UEFI GOP support has been checked into the freebsd/edk2 repo:
>  
> https://github.com/freebsd/uefi-edk2/commit/a36132939e259df79b16699c03c6f1d63c7454b9
> 
> A pre-built bhyve/UEFI binary image with GOP support is available at:
>    https://people.freebsd.org/~grehan/bhyve_uefi/BHYVE_UEFI_20160526.fd
> 
> The new bhyve executable supports some new devices. An example of using 
> them for Windows10 is:
> 
> bhyve \
>     -c 2 \
>     -s 3,ahci-cd,/images/win10_install.iso \
>     -s 4,ahci-hd,/images/win10.img \
>     -s 11,fbuf,tcp=0.0.0.0:5900,w=1600,h=900,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

Attachment: signature.asc
Description: PGP signature

Reply via email to