According to the bhyve/Windows wiki:
The lpc slot needs to be in slot 31, and the block devices bust be in 3, 4,
5, and 6.
I have had luck* booting into the Debian install environment using this
method, as long as you pass "console=ttyS0" to grub at boot time. I believe
you must do the same as well on FreeBSD, with adding the ability to use a
console in /boot/loader.conf

*I have installed Debian VMs utilizing UEFI, however I have not had success
after destroying the VM.
They fail to boot and drop you to that fancy EFI shell.

On Mon, Nov 2, 2015 at 10:13 AM, Roman Bogorodskiy <>

> Hi,
> I'm facing a strange problem with -l bootrom.
> I try to boot a VM this way:
> sudo /usr/sbin/bhyve -l bootrom,/home/novel/uefi/BHYVE_UEFI_20151002.fd
> -c 2 -m 214 -A -I -u -H -P -s 0:0,hostbridge -s
> 2:0,virtio-net,tap0,mac=52:54:00:56:9a:77 -s
> 3:0,ahci-hd,/home/novel/FreeBSD-11.0-CURRENT-amd64.raw  -s 1,lpc -l
> com1,/dev/nmdm0A testvm
> BHYVE_UEFI_20151002.fd is downloaded from [1].
> FreeBSD-11.0-CURRENT-amd64.raw is downloaded from [2].
> VMs fail to boot with 'Boot Failed. EFI Hard Drive' and brings into UEFI
> shell.
> Changing ahci-hd to virtio-blk changes error message to:
> 'Boot Failed. EFI Misc Device'.
> Dropping 'hostbridge' and 'virtio-net' doesn't seem to change anything.
> Also, before trying FreeBSD-11.0-CURRENT-amd64.raw I tried my old images
> I used with bhyveload and they fail in the same way, though they're
> still booting using bhyveload.
> I'm running -CURRENT updated last weekend on Intel i5-2310.
> What could be wrong with this?
> 1:
> 2:
> Roman Bogorodskiy
_______________________________________________ mailing list
To unsubscribe, send any mail to 

Reply via email to