Closed davidak closed 1 year ago
Thanks. Is '/usr/libexec/qemu-bridge-helper' is not a suitable bridge helper: No such file or directory
an error that should be fixed?
So we let the issue open as "known problem" until someone wants to fix it? Or is there anything we can do easily to have a better user experience (aka don't get cryptic error messages)?
It's a problem, but what can we use instead?
Not having VMs isn't a useful alternative.
Adding a
virtualisation.libvirtd.qemuVerbatimConfig = ''
bridge_helper = "${pkgs.qemu}/libexec/qemu-bridge-helper"
''
seems to not help at all. The file at /var/lib/libvirtd/qemu.conf
does get the line in it, but libvirtd itself seems to ignore the configuration entirely and still insists on using /usr/libexec/qemu-bridge-helper
Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
Still a problem on 22.05.
Adding lines suggested above and manually restarting libvirtd service seems to temporarily fix the issue for me.
virtualisation.libvirtd.qemuVerbatimConfig = ''
bridge_helper = "${pkgs.qemu}/libexec/qemu-bridge-helper"
''
However problem arises again after host restart, and a manual restart of libvirtd service is necessary. I use libvirtd running as a user-space daemon (qemu://session). Haven't yet investigated the issue any further.
This seems to be fixed by the already-merged #187211, which I assume should be in upcoming NixOS 22.11. It's working for me on unstable.
Issue description
I configured QEMU/KVM and connect virt-manager via "User session" to start a VM.
The VM has no network connection, so i try to set my ethernet interface as bridge. (I don't know what i'm doing)
Starting the VM fails now with this message:
Steps to reproduce
Technical details
"x86_64-linux"
Linux 4.9.80, NixOS, 17.09.3001.395fe7f8bcb (Hummingbird)
yes
yes
nix-env (Nix) 1.11.16
""
"nixos-17.09.3001.395fe7f8bcb, nixos-hardware"
/nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs