Daniel P. Berrangé wrote:
On Fri, Jul 31, 2026 at 05:53:56PM +0200, Roman Bogorodskiy wrote:
Currently, when the bhyve driver builds capabilities, it uses just "bhyve" as emulator path. That leads to issues, e.g. virt-manager uses this value to fill domain's emulator field, which has to be an absolute path. So that results in a domain XML that fails validation.
Fix by trying to find "bhyve" in PATH and falling back to "/usr/sbin/bhyve".
Closes: https://gitlab.com/libvirt/libvirt/-/work_items/899 Signed-off-by: Roman Bogorodskiy <bogorodskiy@gmail.com> --- src/bhyve/bhyve_capabilities.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Thanks! Should I push it now or wait until after 12.6.0?