Virt-manager: Difference between revisions
imported>BridgerB mNo edit summary |
imported>The-furry-hubofeverything m Added note to explain dconf, numerous issues were created on nixpkgs were related to this |
||
Line 4: | Line 4: | ||
<syntaxhighlight lang="nix"> | <syntaxhighlight lang="nix"> | ||
virtualisation.libvirtd.enable = true; | virtualisation.libvirtd.enable = true; | ||
programs.dconf.enable = true; | programs.dconf.enable = true; # virt-manager requires dconf to remember settings | ||
environment.systemPackages = with pkgs; [ virt-manager ]; | environment.systemPackages = with pkgs; [ virt-manager ]; | ||
</syntaxhighlight> | </syntaxhighlight> |
Revision as of 10:57, 8 October 2023
Installation
NixOS
virtualisation.libvirtd.enable = true;
programs.dconf.enable = true; # virt-manager requires dconf to remember settings
environment.systemPackages = with pkgs; [ virt-manager ];
You will get a warning when you open it for the first time
Could not detect a default hypervisor. Make sure the appropriate QEMU/KVM virtualization packages are installed to manage virtualization on this host.
A virtualization connection can be manually added via File->Add Connection
To resolve
File (in the menu bar) -> Add connection HyperVisor = QEMU/KVM Autoconnect = checkmark Connect
The same can also be achieved decoratively by setting the corresponding dconf settings with home-manager. If you want to do this instead of the imperative configuration described above, add the following snippet to your home-manager configuration:
dconf.settings = {
"org/virt-manager/virt-manager/connections" = {
autoconnect = ["qemu:///system"];
uris = ["qemu:///system"];
};
};
You can get the following error :
authentication unavailable: no polkit agent available to authenticate action 'org.libvirt.unix.manage'
To resolve, add the user to the libvirtd
group.
{
users.users.<myuser>.extraGroups = [ "libvirtd" ];
}