Virt-manager - Revision history

SummerTime: Unable to find 'efi' firmware

2026-02-09T12:05:31Z

Unable to find 'efi' firmware

@@ Line 66: / Line 66: @@
       name = "Vanilla-DMZ";
    };
 [[Category:Virtualization]]

Phobos: Added a note for fixing firewall issues

2026-01-17T22:46:45Z

Added a note for fixing firewall issues

← Older revision		Revision as of 22:46, 17 January 2026
Line 26:		Line 26:
	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">		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">
	# virsh net-autostart default		# virsh net-autostart default
	</syntaxhighlight>By default, this will enable a virtual network bridge under the name <code>virbr0</code>.		</syntaxhighlight>By default, this will enable a virtual network bridge under the name <code>virbr0</code>. You may need to allow it through your firewall filter like so:
			{{File\|3=networking.firewall.trustedInterfaces = [ "virbr0" ];\|name=/etc/nixos/configuration.nix\|lang=nix}}

	=== Display ===		=== Display ===

Phobos at 05:04, 10 December 2025

2025-12-10T05:04:14Z

← Older revision		Revision as of 05:04, 10 December 2025
Line 18:		Line 18:

	=== Networking ===		=== 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}}

	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">		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">
	# virsh net-autostart default		# virsh net-autostart default

Phobos: Updated Formating

2025-12-10T00:52:51Z

Updated Formating

← Older revision		Revision as of 00:52, 10 December 2025
Line 1:		Line 1:
	~~The~~ [https://virt-manager.org/ ~~virt~~-manager] (~~[[wikipedia:en:{{PAGENAME}}]]~~) ~~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~~).		[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).

	== ~~Requisites~~ ==		== Prequisites ==
	~~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.		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>

	~~=== NixOS ===~~		To resolve, add your user to the libvirtd group:

	~~<syntaxhighlight lang="nix">~~
	~~virtualisation.libvirtd.enable = true;~~
	~~programs.virt-manager.enable = true;~~
	~~</syntaxhighlight>~~

	~~You may get the following error:~~

	~~<code>authentication unavailable: no polkit agent available to authenticate action 'org.libvirt.unix.manage'</code>~~

	To resolve, add ~~the~~ user to the ~~<code>~~libvirtd~~</code>~~ group:

	~~<syntaxhighlight lang~~=~~"nix">~~		{{File\|3={
	{
	users.users.<myuser>.extraGroups = [ "libvirtd" ];		users.users.<myuser>.extraGroups = [ "libvirtd" ];
	}		}\|name=/etc/nixos/configuration.nix\|lang=nix}}\|leading=After rebuild, you may get the following error:}}
	</~~syntaxhighlight>~~

	=== Networking ===		=== Networking ===
	The default network starts off ~~as being~~ inactive, you must enable it before it is accessible.		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">
	This can be done by running the following command ~~(may require sudo)~~:		# virsh net-autostart default
			</syntaxhighlight>By default, this will enable a virtual network bridge under the name <code>virbr0</code>.

	~~<code>virsh net-start~~ default~~</code>~~		=== Display ===
			The default video may not allow different resolutions and is limited. It is recommended to use Virtio instead.

	~~Or autostart~~:		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].

	~~<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~~.

	=== Shared folders ===		=== Shared folders ===

Vater at 14:02, 6 July 2025

2025-07-06T14:02:50Z

← Older revision		Revision as of 14:02, 6 July 2025
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).		The [https://virt-manager.org/ virt-manager] ([[wikipedia:en:{{PAGENAME}}]]) 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 ==		== Requisites ==

Jcorbalan: Added an explanation on how to config Virt-manager to be able to share folders with guest VM.

2025-04-03T00:24:24Z

Added an explanation on how to config Virt-manager to be able to share folders with guest VM.

← Older revision		Revision as of 00:24, 3 April 2025
Line 37:		Line 37:
	By default this will enable the <code>virbr0</code> virtual network bridge.		By default this will enable the <code>virbr0</code> virtual network bridge.

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

			=== 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>:

			<syntaxhighlight lang="nix">
			virtualisation.libvirtd = {
			enable = true;
			qemu.vhostUserPackages = with pkgs; [ virtiofsd ];
			};
			</syntaxhighlight>

	===Windows Guest===		===Windows Guest===

Koalp: link to libvirt article

2025-01-03T15:19:08Z

link to libvirt article

← Older revision		Revision as of 15:19, 3 January 2025
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).		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 ==		== Requisites ==

Fugidev: /* Networking */

2024-11-10T14:44:39Z

Networking

← Older revision		Revision as of 14:44, 10 November 2024
Line 27:		Line 27:
	=== Networking ===		=== Networking ===
	The default network starts off as being inactive, you must enable it before it is accessible.		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:		This can be done by running the following command (may require sudo):

	<code>virsh net-start default</code>		<code>virsh net-start default</code>
Line 36:		Line 36:

	By default this will enable the <code>virbr0</code> virtual network bridge.		By default this will enable the <code>virbr0</code> virtual network bridge.

	~~Sorry - this seems out of date. 2024 July 10<syntaxhighlight lang="bash">~~
	~~[das@t14:~/nixos/t14]$ virsh net-autostart default~~
	~~error: failed to get network 'default'~~
	~~error: Network not found: no network with matching name 'default'~~
	~~</syntaxhighlight>~~

	===Display===		===Display===

Mic92: import from old wiki

2024-08-01T12:14:59Z

import from old wiki

← Older revision		Revision as of 12:14, 1 August 2024
Line 55:		Line 55:
	{		{
	services.qemuGuest.enable = true;		services.qemuGuest.enable = true;
			services.spice-vdagentd.enable = true; # enable copy and paste between host and guest
	}		}
	</syntaxhighlight>		</syntaxhighlight>

Randomizedcoder: /* Networking */ Comment about documentation issue

2024-07-10T15:35:13Z

Networking: Comment about documentation issue

← Older revision		Revision as of 15:35, 10 July 2024
Line 36:		Line 36:

	By default this will enable the <code>virbr0</code> virtual network bridge.		By default this will enable the <code>virbr0</code> virtual network bridge.

			Sorry - this seems out of date. 2024 July 10<syntaxhighlight lang="bash">
			[das@t14:~/nixos/t14]$ virsh net-autostart default
			error: failed to get network 'default'
			error: Network not found: no network with matching name 'default'
			</syntaxhighlight>

	===Display===		===Display===