I am very proud and pleased to announce the general availability of GitHub - SaumonNet/proxmox-nixos: The Proxmox Hypervisor, on NixOS [maintainers=@camillemndn @julienmalka], a port of Proxmox for NixOS made by Camille Mondon (camillemndn (Camille Mondon) · GitHub) and myself (JulienMalka (Julien Malka) · GitHub).
The project is still in early development and might have some rough edges, but we would be very happy to have our first beta testers!
This is very exciting! I was expecting only x86 being supported but I’m happy to be proven wrong with arm64 support. Thank you!
Would love to hear a feedback on how it’s working on aarch64!
As someone who’s just bumping up against the limitations of lxd/incus, this is very interesting, thank you! Do I take it it’s using the default nixos kernel?
Really exciting to see this, as this has been one of the largest pain points remaining in my network - given its the only device without declarative configuration!
If you need beta testers and have a Matrix room or similar I’d be happy to try things out if that’s helpful.
One question I have is the mentions in the README that you need to set configuration declaratively and also in the WEBUI “to keep Proxmox happy” - could you expand on that?
In other words I could just rely on the nix config to stand up an exact replica server, it’s just that the WEBUI wouldn’t show the applied config?
Currently (and we might fix ça in the future) the Proxmox web UI cannot detect the interfaces that exists on your system from your NixOS configuration. That poses a problem when you try to add a virtual network interface to a VM through the UI because then it doesn’t list the bridges that you could connect it to. The fix here is simply to create a bridge through the web interface (you only have to do it once) and then Proxmox will think it is handling the configuration of this bridge (while it is actually your NixOS configuration).
We’d be really happy with beta testers. For further discussions I created a matrix room here: https://matrix.to/#/#proxmox-nixos:matrix.org
nixos/pkgs/python3Packages/ifupdown2/default.nix at 4a060976a5a3774c6a4882ca8ec871e4e3cc9505 · Lillecarl/nixos · GitHub ifupdown2 for NixOS 
This is really exciting! Out of curiosity, are you interacting with the upstream project any as it relates to this project?
Are you guys planning to upstream this into nixpkgs at some point? I understand it’s experimental right now. But I personally run Proxmox quite a bit, and I’d love to see this become really usable in production. Which for me means that I would not have to rely on a third-party cache.
Exciting. What “balance” of iterative/declarative configuration are you targeting, if any? For example, will it be possible to declare a full system as per usual, but allow iterative changes via WUI/CLI that are restored on a reboot?
does iommu passthrough work?
Im definitely considering using this.
Is this home-lab ready?
I use proxmox and have quite liberal use of the LVM / PBS, etc.
I would use microvm if I had a web interface so im kinda stuck on proxmox.
I’ve got it up and running! I’m about to get started building and configuring and moving a Raspberry Pi 4B and Pi Zero W into this thing (I mean virtualize the things I use the Pi’s for). I only seem to have one question as I get up and running: would there be any benefit to purchasing a Proxmox subscription? I would be happy to support the Proxmox team with a community subscription, but I’m wondering if this “Proxmox on NixOS” uses its own repository instead of the community edition, nullifying the “Access to Enterprise repository” benefit.
Thanks in advance for your response. Thank you for your hard work, and please let me know if there is any information from my system that may be useful to this project!
If this is not the appropriate place to post this, please let me know.
I want to get a dns challenged cert installed:
TASK ERROR: Registration failed: Can't locate object method "bless_pointer" via package "Crypt::OpenSSL::Bignum" at blib/lib/Crypt/OpenSSL/RSA.pm (autosplit into blib/lib/auto/Crypt/OpenSSL/RSA/get_key_parameters.al) line 330.
I’m not exactly sure what to look for, and the cert is not a huge deal, but I would greatly appreciate any pointers to send me on my way to troubleshoot this issue