On launch of Boxes on Fedora 30 and Rawhide, an authentication prompt for "firewall direct interface" appears. This started happening between Fedora-30-20190301.n.0 and Fedora-30-20190312.n.0, it seems. I'm not sure whether it's intended / expected?
This is a libvirt regression, I think you'll get the prompt too if you interact with qemu:///session with virsh. libvirt people are aware of it.
libvirt-5.1.0-3.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f3e6d3e0a5
Upstream fix is commit 3e02ee9b5da7fc7197aaa6d57563349a7670b8a1 (origin/v5.1.0-maint, v5.1.0-maint) Author: Daniel P. Berrangé <berrange> Date: Wed Mar 13 16:21:15 2019 +0000 network: avoid trying to create global firewall rules if unprivileged The unprivileged libvirtd does not have permission to create firewall rules, or bridge devices, or do anything to the host network in general. Historically we still activate the network driver though and let the network start API call fail. The startup code path which reloads firewall rules on active networks would thus effectively be a no-op when unprivileged as it is impossible for there to be any active networks With the change to use a global set of firewall chains, however, we now have code that is run unconditionally. Ideally we would not register the network driver at all when unprivileged, but the entanglement with the virt drivers currently makes that impractical. As a temporary hack, we just make the firewall reload into a no-op. Signed-off-by: Daniel P. Berrangé <berrange>
libvirt-5.1.0-3.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.