Jump to content

Virt-manager: Difference between revisions

From Official NixOS Wiki
imported>Artturin
add virt-manager page and instructions
 
Phobos (talk | contribs)
mNo edit summary
 
(27 intermediate revisions by 22 users not shown)
Line 1: Line 1:
[https://virt-manager.org/ Virt-manager] (a.k.a. Virtual Machine Manager) is a GUI application for managing local and remote virtual machines through [[libvirt]]. It primarily targets KVM VMs, but also manages Xen and LXC (Linux Containers).
== Prequisites ==
Though Virt-manager (using the KVM hypervisor) is able to take advantage of virtualisation capabilities without any UEFI/BIOS configuration, best performance demands that the host have Vt-x and Vt-d (Intel) or AMD-V and AMD-Vi (AMD) enabled.
These settings can usually be found under the UEFI/BIOS settings.
== Installation ==
== Installation ==
In your configuration file add:
{{File|3=virtualisation.libvirtd.enable = true;
programs.virt-manager.enable = true;|name=/etc/nixos/configuration.nix|lang=nix}}{{Note|<br/><br /><code>authentication unavailable: no polkit agent available to authenticate action 'org.libvirt.unix.manage'</code>
To resolve, add your user to the libvirtd group:
{{File|3={
  users.users.<myuser>.extraGroups = [ "libvirtd" ];
}|name=/etc/nixos/configuration.nix|lang=nix}}|leading=After rebuild, you may get the following error:}}
=== Networking ===
To use the default libvirt network, you will need to install the <code>dnsmasq</code> package. This is required for DNS and DCHP functionality within the network:
{{File|3=environment.systemPackages = with pkgs; [
  dnsmasq
];|name=/etc/nixos/configuration.nix|lang=nix}}


=== NixOS ===
The default network starts off inactive, you must enable it before it is accessible. This can be done by running the following command: <syntaxhighlight lang="console"># virsh net-start default</syntaxhighlight>And if you would like to enable it automatically at boot:<syntaxhighlight lang="console">
<syntaxhighlight lang="nix">
# virsh net-autostart default
virtualisation.libvirtd.enable = true;
</syntaxhighlight>By default, this will enable a virtual network bridge under the name <code>virbr0</code>.
programs.dconf.enable = true;
environment.systemPackages = with pkgs; [ virt-manager ]
</syntaxhighlight>


You will get a warning when you open it for the first time
=== Display ===
The default video may not allow different resolutions and is limited. It is recommended to use Virtio instead.


<code>Could not detect a default hypervisor. Make sure the appropriate virtualization packages containing kvm, qemu, libvirt, etc. are installed and that libvirtd is running.</code>
For information on how to use Virtio with your VM's, [https://wiki.libvirt.org/Virtio.html you can read up on Virtio on the libvirt wiki].


To resolve
=== Shared folders ===
To be able to share a folder with a guest, you will need 'virtiofsd'. The recommended way to solve this problem is now to add <code>pkgs.virtiofsd</code> to <code>virtualisation.libvirtd.qemu.vhostUserPackages</code>:


<pre>
<syntaxhighlight lang="nix">
File in the menu bar -> Add connection
virtualisation.libvirtd = {
  enable = true;
  qemu.vhostUserPackages = with pkgs; [ virtiofsd ];
};
</syntaxhighlight>


HyperVisor = QEMU/KVM
===Windows Guest===
Autoconnect = checkmark
See [https://github.com/virtio-win/virtio-win-guest-tools-installer Virtio-win guest tools] for additional drivers for both paravirtual and emulated hardware


Connect
===Guest Agent===
</pre>
When running NixOS as a guest, enable the [https://wiki.qemu.org/Features/GuestAgent QEMU guest agent] with:
 
<syntaxhighlight lang="nix">
{
  services.qemuGuest.enable = true;
  services.spice-vdagentd.enable = true;  # enable copy and paste between host and guest
}
</syntaxhighlight>


You will only need to do this once
The host must [https://wiki.libvirt.org/Qemu_guest_agent.html#setting-qemu-ga-up provide the needed virtio serial port] under the special name <code>org.qemu.guest_agent.0</code>.


=== Wayland ===
In order to run on Wayland, virt-manager must be ran under XWayland with `$ GDK_BACKEND=x11 virt-manager` or a gdk cursor must be set. An example of setting a gdk cursor with home-manager is as follows:
  home.pointerCursor = {
    gtk.enable = true;
    package = pkgs.vanilla-dmz;
    name = "Vanilla-DMZ";
  };
[[Category:Virtualization]]
[[Category:Virtualization]]

Latest revision as of 05:04, 10 December 2025

Virt-manager (a.k.a. Virtual Machine Manager) is a GUI application for managing local and remote virtual machines through libvirt. It primarily targets KVM VMs, but also manages Xen and LXC (Linux Containers).

Prequisites

Though Virt-manager (using the KVM hypervisor) is able to take advantage of virtualisation capabilities without any UEFI/BIOS configuration, best performance demands that the host have Vt-x and Vt-d (Intel) or AMD-V and AMD-Vi (AMD) enabled.

These settings can usually be found under the UEFI/BIOS settings.

Installation

In your configuration file add:

❄︎ /etc/nixos/configuration.nix
virtualisation.libvirtd.enable = true;
programs.virt-manager.enable = true;
After rebuild, you may get the following error:

authentication unavailable: no polkit agent available to authenticate action 'org.libvirt.unix.manage'

To resolve, add your user to the libvirtd group:

❄︎ /etc/nixos/configuration.nix
{
  users.users.<myuser>.extraGroups = [ "libvirtd" ];
}

Networking

To use the default libvirt network, you will need to install the dnsmasq package. This is required for DNS and DCHP functionality within the network:

❄︎ /etc/nixos/configuration.nix
environment.systemPackages = with pkgs; [ 
  dnsmasq 
];

The default network starts off inactive, you must enable it before it is accessible. This can be done by running the following command:

# virsh net-start default

And if you would like to enable it automatically at boot:

# virsh net-autostart default

By default, this will enable a virtual network bridge under the name virbr0.

Display

The default video may not allow different resolutions and is limited. It is recommended to use Virtio instead.

For information on how to use Virtio with your VM's, you can read up on Virtio on the libvirt wiki.

Shared folders

To be able to share a folder with a guest, you will need 'virtiofsd'. The recommended way to solve this problem is now to add pkgs.virtiofsd to virtualisation.libvirtd.qemu.vhostUserPackages:

virtualisation.libvirtd = {
  enable = true;
  qemu.vhostUserPackages = with pkgs; [ virtiofsd ];
};

Windows Guest

See Virtio-win guest tools for additional drivers for both paravirtual and emulated hardware

Guest Agent

When running NixOS as a guest, enable the QEMU guest agent with:

{
  services.qemuGuest.enable = true;
  services.spice-vdagentd.enable = true;  # enable copy and paste between host and guest
}

The host must provide the needed virtio serial port under the special name org.qemu.guest_agent.0.

Wayland

In order to run on Wayland, virt-manager must be ran under XWayland with `$ GDK_BACKEND=x11 virt-manager` or a gdk cursor must be set. An example of setting a gdk cursor with home-manager is as follows:

 home.pointerCursor = {
    gtk.enable = true;
    package = pkgs.vanilla-dmz;
    name = "Vanilla-DMZ";
 };