Virt-manager: Difference between revisions

Latest revision as of 14:44, 10 November 2024

The virt-manager application is a GUI for managing local and remote virtual machines through libvirt. It primarily targets KVM VMs, but also manages Xen and LXC (linux containers).

Requisites

Even though Virt-manager (using the KVM hypervisor) is able to take advantage of virtualisation capabilities without any UEFI/BIOS configuration, best performances demand that 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

NixOS

virtualisation.libvirtd.enable = true;
programs.virt-manager.enable = true;

You may 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" ];
}

Networking

The default network starts off as being inactive, you must enable it before it is accessible. This can be done by running the following command (may require sudo):

virsh net-start default

Or autostart:

virsh net-autostart default

By default this will enable the virbr0 virtual network bridge.

Display

The default Video may not allow different resolutions, `Virtio` will allow for more.

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";
 };

@@ Line 1: / Line 1: @@
+The [https://virt-manager.org/ virt-manager] application is a GUI for managing local and remote virtual machines through libvirt. It primarily targets KVM VMs, but also manages Xen and LXC (linux containers).
 == Requisites ==
 Even though Virt-manager (using the KVM hypervisor) is able to take advantage of virtualisation capabilities without any UEFI/BIOS configuration, best performances demand that 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.
@@ Line 5: / Line 7: @@
 === NixOS ===
-Before 23.11:
-<syntaxhighlight lang="nix">
-virtualisation.libvirtd.enable = true;
-programs.dconf.enable = true; # virt-manager requires dconf to remember settings
-environment.systemPackages = with pkgs; [ virt-manager ];
-</syntaxhighlight>
-After 23.11:
 <syntaxhighlight lang="nix">
 virtualisation.libvirtd.enable = true;
 programs.virt-manager.enable = true;
-</syntaxhighlight>
-See [https://github.com/NixOS/nixpkgs/pull/261474 relevant merge request]
-You will get a warning when you open it for the first time:
-<code>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</code>
-To resolve:
-<pre>
-File (in the menu bar) -> Add connection
-HyperVisor = QEMU/KVM
-Autoconnect = checkmark
-Connect
-</pre>
-The same can also be achieved declaratively 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:
-<syntaxhighlight lang="nix">
-dconf.settings = {
-  "org/virt-manager/virt-manager/connections" = {
-    autoconnect = ["qemu:///system"];
-    uris = ["qemu:///system"];
-  };
-};
 </syntaxhighlight>
@@ Line 61: / Line 27: @@
 === Networking ===
 The default network starts off as being inactive, you must enable it before it is accessible.
-This can be done by running the following command: <code>virsh net-start default</code>.
+This can be done by running the following command (may require sudo):
+<code>virsh net-start default</code>
+Or autostart:
+<code>virsh net-autostart default</code>
 By default this will enable the <code>virbr0</code> virtual network bridge.
+===Display===
+The default Video may not allow different resolutions, `Virtio` will allow for more.
+===Windows Guest===
+See [https://github.com/virtio-win/virtio-win-guest-tools-installer Virtio-win guest tools] for additional drivers for both paravirtual and emulated hardware
 ===Guest Agent===
@@ Line 71: / Line 49: @@
 {
    services.qemuGuest.enable = true;
+  services.spice-vdagentd.enable = true;  # enable copy and paste between host and guest
 }
 </syntaxhighlight>
@@ Line 76: / Line 55: @@
 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]]