forked from mirrors/nixpkgs
c738e61a94
According to the QEMU documentation, virtiofsd is supposed to be run directly by users. It therefore makes sense to have it in bin/, so it will be in PATH. Such a change wouldn't make sense upstream, because it would then conflict with the virtiofsd package, which is generally preferred if available. But in Nixpkgs, we don't have to worry about that and can just make QEMU's virtiofsd a lower priority than the one from the dedicated package. [1]: https://qemu.readthedocs.io/en/latest/tools/virtiofsd.html Fixes: https://github.com/NixOS/nixpkgs/issues/113172 ("QEmu: virtiofsd prone to be garbage collected.") Fixes: https://github.com/NixOS/nixpkgs/pull/153007 ("nixos/libvirtd: add ${cfg.qemu.package}/libexec to PATH") |
||
---|---|---|
.. | ||
aqemu | ||
arion | ||
buildkit-nix | ||
catatonit | ||
charliecloud | ||
cloud-hypervisor | ||
cntr | ||
colima | ||
conmon | ||
containerd | ||
cri-o | ||
crosvm | ||
crun | ||
docker | ||
docker-compose | ||
docker-slim | ||
driver | ||
dumb-init | ||
ecs-agent | ||
firecracker | ||
firectl | ||
gvisor | ||
ignite | ||
imgcrypt | ||
libgovirt | ||
libnvidia-container | ||
lima | ||
lkl | ||
looking-glass-client | ||
nvidia-container-runtime | ||
nvidia-container-toolkit | ||
nvidia-docker | ||
nvidia-podman | ||
open-vm-tools | ||
OVMF | ||
podman | ||
podman-compose | ||
podman-tui | ||
qboot | ||
qemu | ||
qtemu | ||
railcar | ||
remotebox | ||
runc | ||
seabios | ||
singularity | ||
spice-vdagent | ||
spike | ||
tini | ||
umoci | ||
virt-manager | ||
virt-top | ||
virt-viewer | ||
virt-what | ||
virtualbox | ||
vpcs | ||
x11docker | ||
xen | ||
xhyve |