Open lheckemann opened 7 years ago
might check here: https://nixos.org/nixops/manual/#idm140737318345376 this might be a "dumb comment", but don't you need a "logical" (what I think the file you show is) and "physical" specification? Perhaps it would give you an error when trying to create the deployment if you didn't have one.
What I have there is effectively a physical specification. The logical specification is empty because I haven't added anything to it, so it'll just be a default nixos install.
Regardless, all deployments to libvirtd that I've tried fail with this same error message — this is the minimal case I reduced it to.
ah yes sorry, it has been a month or two since I messed with nixops. If you wish to continue debugging yourself, one way you could go about it is to look in this file: https://github.com/NixOS/nixops/blob/master/nixops/backends/libvirtd.py you could try recreating commands with virsh/qemu-img manually, or perhaps just adding "print" statements everywhere e.g.: self._logged_exec(["virsh", "-c", "qemu:///system", "create", dom_file]) one thing that might also be helpful for anyone else that reads this issue is, what version of nixops are you using (also perhaps what os?) I have successfully deployed libvirt with nixops before, though my version is somewhat old. though when I did "nix-env -qaP * | fgrep -i nixops" I got this: nixpkgs.nixops nixops-1.4 nixos.nixops nixops-1.4 nixpkgs.nixopsUnstable nixops-2016-11-23
and if nixops unstable is the latest unstable channel version of nixops (looks to be 1.4 if it's from november), I have used that one to deploy libvirt successfully, (my os is nixos, I follow the stable channel, which is currently 17.03) though not without problems when deploying more than one machine, see https://github.com/NixOS/nixops/issues/617 (I use a hack to work around this problem, (closed) pull request mentioned in issue)
the libvirt implementation has also had problems in the past with permissions and having to work around security features, so that would be something to be aware of as well.
Hah, removing qemu from my profile fixed it...
While trying to deploy
I get (after a successful build):