Libvirt - Revision history

Jaythomas: Add section "File sharing via virtiofs mount"

2026-04-26T23:30:12Z

Add section "File sharing via virtiofs mount"

@@ Line 118: / Line 118: @@
 The host should now be able to reach the guest via the bridge interface and vice versa.
-=== File sharing ===
+=== File sharing via virtiofs mount ===
-In order to share files between host and guest, one recommended way is to use <code>spice-webdavd</code>.
+==== Error starting domain: internal error: Child process (/run/current-system/sw/bin/virtiofsd --print-capabilities) unexpected exit status 127: libvirt:  error : cannot execute binary /run/current-system/sw/bin/virtiofsd: No such file or directory ====
 Shutdown the client, in this example named <code>my_guest</code>, and edit the libvirt XML file.

Marie: dnsmasq is provided in the package by default and does not need installation.

2026-02-13T09:24:16Z

dnsmasq is provided in the package by default and does not need installation.

← Older revision		Revision as of 09:24, 13 February 2026
Line 47:		Line 47:
	==== Default networking ====		==== Default networking ====

	~~To utilize the default libvirt network, you will need to install the {{nixos:package\|dnsmasq}} package. This is required for DNS and DCHP functionality within the network:~~		Enable and start the default network using the following commands:

	~~{{File\|3=environment.systemPackages = with pkgs; [~~
	~~dnsmasq~~
	~~];\|name=/etc/nixos/configuration.nix\|lang=nix}}~~

	~~Once the package is installed, enable~~ and start the default network using the following commands:

	<syntaxhighlight lang="console">		<syntaxhighlight lang="console">

Sandro: /* Nested virtualization */

2026-01-18T09:55:29Z

Nested virtualization

← Older revision		Revision as of 09:55, 18 January 2026
Line 38:		Line 38:

	{{file\|\|\|<nowiki>		{{file\|\|\|<nowiki>
	boot.extraModprobeConfig = "options kvm_intel nested=1";		boot.extraModprobeConfig = ''
			options kvm_intel nested=1
			'';
	</nowiki>\|name=/etc/nixos/configuration.nix\|lang=nix}}		</nowiki>\|name=/etc/nixos/configuration.nix\|lang=nix}}

Phobos: Minor note on firewall whitelisting

2026-01-17T22:48:47Z

Minor note on firewall whitelisting

← Older revision		Revision as of 22:48, 17 January 2026
Line 58:		Line 58:
	</syntaxhighlight>		</syntaxhighlight>

	This will configure the default network to start automatically on boot and immediately activate it.		This will configure the default network to start automatically on boot and immediately activate it. You may need to whitelist the interface for the firewall like so:

			{{File\|3=networking.firewall.trustedInterfaces = [ "virbr0" ];\|name=/etc/nixos/configuration.nix\|lang=nix}}

	==== Bridge networking ====		==== Bridge networking ====

Zimward: add note that virt-manager needs swtpm in path to use emulated tpm

2025-12-20T09:48:57Z

add note that virt-manager needs swtpm in path to use emulated tpm

← Older revision		Revision as of 09:48, 20 December 2025
Line 9:		Line 9:

	# Enable TPM emulation (optional)		# Enable TPM emulation (optional)
			# install pkgs.swtpm system-wide for use in virt-manager (optional)
	virtualisation.libvirtd.qemu = {		virtualisation.libvirtd.qemu = {
	swtpm.enable = true;		swtpm.enable = true;

Zimward: OVMF submodule has been removed

2025-12-20T09:27:56Z

OVMF submodule has been removed

← Older revision		Revision as of 09:27, 20 December 2025
Line 5:		Line 5:
	Enable libvirt daemon		Enable libvirt daemon

	{{file\|~~/etc/nixos/configuration.nix~~\|~~nix~~\|<nowiki>		{{file\|\|\|<nowiki>
	virtualisation.libvirtd.enable = true;		virtualisation.libvirtd.enable = true;

Line 11:		Line 11:
	virtualisation.libvirtd.qemu = {		virtualisation.libvirtd.qemu = {
	swtpm.enable = true;		swtpm.enable = true;
	~~ovmf.packages = [ pkgs.OVMFFull.fd ];~~
	};		};

Line 17:		Line 16:
	virtualisation.spiceUSBRedirection.enable = true;		virtualisation.spiceUSBRedirection.enable = true;

	</nowiki>}}		</nowiki>\|name=/etc/nixos/configuration.nix\|lang=nix}}

	To enable local user access to libvirt, for example by using <code>virt-manager</code> or <code>gnome-boxes</code>, add yourself to the <code>libvirtd</code> group		To enable local user access to libvirt, for example by using <code>virt-manager</code> or <code>gnome-boxes</code>, add yourself to the <code>libvirtd</code> group

Phobos: Updated Formating

2025-12-10T05:01:42Z

Updated Formating

← Older revision		Revision as of 05:01, 10 December 2025
Line 37:		Line 37:
	If you would like to enable nested virtualization for your guests to run KVM hypervisors inside them, you should enable it as follows: {{nixos:option\|boot.extraModprobeConfig}}, for example:		If you would like to enable nested virtualization for your guests to run KVM hypervisors inside them, you should enable it as follows: {{nixos:option\|boot.extraModprobeConfig}}, for example:

	{{file\|~~/etc/nixos/configuration.nix~~\|~~xml~~\|<nowiki>		{{file\|\|\|<nowiki>
	boot.extraModprobeConfig = "options kvm_intel nested=1";		boot.extraModprobeConfig = "options kvm_intel nested=1";
	</nowiki>}}		</nowiki>\|name=/etc/nixos/configuration.nix\|lang=nix}}

	=== Networking ===		=== Networking ===
Line 45:		Line 45:
	==== Default networking ====		==== Default networking ====

	To utilize the default libvirt network, you will need to install the {{nixos:package\|dnsmasq}} package. This is required for DNS and DCHP functionality within the network.		To utilize the default libvirt network, you will need to install the {{nixos:package\|dnsmasq}} 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}}

	Once the package is installed, enable and start the default network using the following commands:		Once the package is installed, enable and start the default network using the following commands:
Line 58:		Line 62:
	==== Bridge networking ====		==== Bridge networking ====

	Create a XML file called <code>virbr0.xml</code> with the definition of the bridge interface		Create a XML file called <code>virbr0.xml</code> with the definition of the bridge interface.

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
Line 68:		Line 72:
	</syntaxhighlight>		</syntaxhighlight>

	Add and enable bridge interface		Add and enable bridge interface.

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
Line 78:		Line 82:
	</syntaxhighlight>		</syntaxhighlight>

	Edit the libvirt guest <code>my_guest</code> XML file and add the bridge interface to it		Edit the libvirt guest <code>my_guest</code> XML file and add the bridge interface to it.

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
Line 84:		Line 88:
	</syntaxhighlight>		</syntaxhighlight>

	Add		Add:

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
Line 99:		Line 103:
	</syntaxhighlight>		</syntaxhighlight>

	Inside the guest configure networking for the interface <code>enp1s0</code> (name ~~might~~ differ)		Inside the guest configure networking for the interface <code>enp1s0</code> (name may differ).

	{{file\|/etc/nixos/configuration.nix\|nix\|<nowiki>		{{file\|/etc/nixos/configuration.nix\|nix\|<nowiki>
Line 118:		Line 122:
	=== File sharing ===		=== File sharing ===

	In order to share files between host and guest, one recommended way ~~of doing this~~ is to use <code>spice-webdavd</code>.		In order to share files between host and guest, one recommended way is to use <code>spice-webdavd</code>.

	Shutdown the client, in this example named <code>my_guest</code>, and edit the libvirt XML file.		Shutdown the client, in this example named <code>my_guest</code>, and edit the libvirt XML file.
Line 136:		Line 140:
	</syntaxhighlight>		</syntaxhighlight>

	Start the guest machine. Inside the guest, add following part to your system configuration and apply it		Start the guest machine. Inside the guest, add following part to your system configuration and apply it.

	{{file\|/etc/nixos/configuration.nix\|nix\|<nowiki>		{{file\|/etc/nixos/configuration.nix\|nix\|<nowiki>
Line 142:		Line 146:
	</nowiki>}}		</nowiki>}}

	List available shares for the guest		List available shares for the guest.

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
Line 148:		Line 152:
	</syntaxhighlight>		</syntaxhighlight>

	Mount an example share called <code>myshare</code> to the mountpoint <code>myshare</code>		Mount an example share called <code>myshare</code> to the mountpoint <code>myshare.</code>

	{{file\|/etc/nixos/configuration.nix\|nix\|<nowiki>		{{file\|/etc/nixos/configuration.nix\|nix\|<nowiki>

Pigs: /* Configuration */ Add default networking section and pci passthrough section

2025-05-12T21:08:02Z

Configuration: Add default networking section and pci passthrough section

@@ Line 41: / Line 41: @@
 </nowiki>}}
-=== Bridge networking ===
+=== Networking ===
 Create a XML file called <code>virbr0.xml</code> with the definition of the bridge interface
@@ Line 180: / Line 195: @@
 systemctl start libvirtd-config.service
 </syntaxhighlight>
 == Clients ==

Pablo1107: Added a note for why you won't find hooks files after switching.

2025-01-25T07:14:06Z

Added a note for why you won't find hooks files after switching.

← Older revision		Revision as of 07:14, 25 January 2025
Line 177:		Line 177:
	};		};
	}		}
			</syntaxhighlight>Note that after you added the configuration and switch, you'll have the following command to setup the hooks.<syntaxhighlight lang="bash">
			systemctl start libvirtd-config.service
	</syntaxhighlight>		</syntaxhighlight>

	== Clients ==		== Clients ==

Pablo1107: /* Hooks */

2025-01-25T06:57:18Z

Hooks

← Older revision		Revision as of 06:57, 25 January 2025
Line 150:		Line 150:
	</nowiki>}}		</nowiki>}}

	==== Hooks ====		=== Hooks ===
	Libvirt allows the use of hooks to run custom scripts during specific events, such as daemon lifecycle events, domain lifecycle events, and network events. On NixOS, you can configure hooks via the NixOS module to automate the placement of hook scripts in the appropriate directories.		Libvirt allows the use of hooks to run custom scripts during specific events, such as daemon lifecycle events, domain lifecycle events, and network events. On NixOS, you can configure hooks via the NixOS module to automate the placement of hook scripts in the appropriate directories.