PÁLI Gábor János

In the meantime, you could try to boot your FreeBSD system with verbose messages and check `dmesg` for information about the MSI allocation and activation. Maybe it will show why...

I have done some further investigation, and it seems that `pciconf` itself could be used to send commands to PCI devices with the `-w` flag (and replace `setpci`). But since...

Another update. Looks like one does not have to unload `vmm`, it is enough if no `bhyve` VM runs with PCI pass-through configured in order to get the `MSI: Enable-`...

Thanks for reporting the issue! Personally, I could not reproduce this. On my 13.4 system, the second invocation to `wifibox console` gives a error. ```console # wifibox console Connecting, type...

I could not reproduce this issue on a freshly installed 14.1-RELEASE system either.

> There is a problem remaining with the patch. `vm_manager()` calls `destroy_vm()` always after bhyvectl is started, and possibly `destroy_nmdm()` and `destroy_bridge()` Yes, I have noticed the same issue while...

> Just to confirm: are you satisfied that there is no condition that the VM manager exits somehow without restarting, and we don't want to call `destroy_bridge()`? For example if...

I have got some warnings from [ShellCheck](https://www.shellcheck.net/) (by running the `make shellcheck` command): ```console In sbin/wifibox line 727: trap _kill_child SIGTERM ^-----^ SC3048 (warning): In POSIX sh, prefixing signal names...

> I've fixed the Shellcheck warnings, and fixed three calls to `kill -SIGTERM` as well. There was already one `kill -TERM`, fyi. Thanks! Curiously, ShellCheck did not give a warning...

> [T]oday I realized there is a more elegant solution to solving this bug than creating the (local) whole function for it. I like this solution! Let us do that,...