Libvirtd error in unstable

Help
1

Hi,
Since yesterday, I’m getting an error with virtualisation.libvirtd.enable. It reports a “failed assertion: The ‘virtualisation.libvirtd.qemu.ovmf’ submodule has been removed”. Indeed, this option which exists in 25.05 does not exist in unstable, which is what I am following. I have made no changes in this regard, just updated my flake, and experienced the error. Is anyone else experiencing this?
Brian

2

Could be:

3 Likes
3

Thanks, I’ll check it out.

4

I read through the thread and I kind of understood it, although it is still unclear how to enable libvirt and make the error message go away. I just want to be able to run vms from time to time. Perhaps I don’t even need it?

5

What is your config? I got that and removed the OMVF submodule and I’m back to normally. Though I don’t have any workloads currently on it (since mine are periodic and transient).

6

I’m not explicitly adding the submodule, so I don’t know how to remove it. If I remove libvirt.enable = true the error goes away.

  virtualisation = {
    libvirtd.enable = true;
    podman = {
      enable = true;
      dockerCompat = true;
      defaultNetwork.settings.dns_enabled = true;
    };
    containers.enable = true;
  };
7

I wonder if it’s a bug in nixpkgs on the version you’re on, potentially. I had updated my nixpkgs recently, which had me have to remove that submodule which fixed the message. However, I reverted in the face of the cmake build failures tearing through the ecosystem. Have you updated whatever channel or input provides your nixpkgs? Also, it’s possible something else is requesting and setting that option, but we won’t be able to see without the full config file.

8

I use flakes and am pinned to unstable.

9

Is it still happening after flake updates? If so, got your flake posted somewhere? This sounds not like a config issue but genuine bug, where something else has that option set that shouldn’t.

1 Like
10

Thanks for the replies. I’m actually not using it anymore, so haven’t pursued the issue. For a lark, I tried adding it back to my configuration, but I get the same error. Since I don’t need it now, I don’t really want to spend time pursuing it unless others experience it as well.