port was introduced back in FreeBSD 11.0 way back
in Sept 2016:
https://www.freebsd.org/releases/11.0R/relnotes.html#hardware-
virtualization
Thanks to Peter Graham on FreeBSD virtualization bug tracker for helping
to find source of problem.
Should this BUG go to KVM / QEMU upstream ?
Cheers,
Joh
** Summary changed:
- Ubuntu 20.04 QEMU Failure with nested FreeBSD bhyve
+ Ubuntu 20.04 KVM / QEMU Failure with nested FreeBSD bhyve
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1876678
Title:
Public bug reported:
BUG:
Starting FreeBSD Layer 2 bhyve Guest within Layer 1 FreeBSD VM Host on
Layer 0 Ubuntu 20.04 KVM / QEMU Host result in Layer 1 Guest / Host
Pausing with "Emulation Failure"
TESTING:
My test scenario is nested virtualisation:
Layer 0 - Ubuntu 20.04 Host
Layer 1 - FreeBSD
