KVM - Revision history

Prabuanand: fixed wikitags

2025-05-09T05:15:35Z

fixed wikitags

← Older revision		Revision as of 05:15, 9 May 2025
Line 6:		Line 6:
	# rc-update add libvirtd</nowiki>}}		# rc-update add libvirtd</nowiki>}}

	~~== Starting Libvirtd ==~~		To start the {{ic\|libvirtd}} service immediately, run the [[OpenRC]] command: {{Cmd\|# rc-service libvirtd start}}
	To ~~make~~ the libvirtd service ~~start~~, run the ~~following~~:
	{{Cmd\|# rc-service libvirtd start}}

	== Networking ==		== Networking ==
	~~By default, libvirt uses NAT for VM connectivity. If you want to use the default configuration, you need to load the tun module.~~
	~~{{Cmd\|# modprobe tun}}~~

	~~Add~~ tun ~~to autostart~~:		By default, libvirt uses NAT for VM connectivity. If you want to use the default configuration, load the tun module:{{Cmd\|# modprobe tun}}
	{{Cmd\|# ~~echo "tun" >> /etc/modules-load.d/~~tun~~.conf~~}}

	To make the tun module load on boot, use this command:		Add tun to autostart: {{Cmd\|# echo "tun" >> /etc/modules-load.d/tun.conf}}
	{{Cmd\|# cat /etc/modules {{!}} grep tun {{!}}{{!}} echo tun >> /etc/modules}}
			To make the tun module load on boot, use this command: {{Cmd\|# cat /etc/modules {{!}} grep tun {{!}}{{!}} echo tun >> /etc/modules}}

	If you prefer bridging a guest over your Ethernet interface, you need to make a [[Bridge#Configuration_file\|bridge]].		If you prefer bridging a guest over your Ethernet interface, you need to make a [[Bridge#Configuration_file\|bridge]].
Line 30:		Line 26:

	== Management ==		== Management ==

	For non-root management, you will need to add your user to the libvirt group.		For non-root management, you will need to add your user to the libvirt group.
	{{Cmd\|# addgroup user libvirt}}		{{Cmd\|# addgroup user libvirt}}

Sprungles: Changed to making a dedicated section. Doesn't quite have to do with Networking.

2025-05-08T14:25:20Z

Changed to making a dedicated section. Doesn't quite have to do with Networking.

← Older revision		Revision as of 14:25, 8 May 2025
Line 5:		Line 5:
	{{Cmd\|<nowiki># apk add libvirt-daemon qemu-img qemu-system-x86_64 qemu-modules openrc		{{Cmd\|<nowiki># apk add libvirt-daemon qemu-img qemu-system-x86_64 qemu-modules openrc
	# rc-update add libvirtd</nowiki>}}		# rc-update add libvirtd</nowiki>}}

			== Starting Libvirtd ==
			To make the libvirtd service start, run the following:
			{{Cmd\|# rc-service libvirtd start}}

	== Networking ==		== Networking ==
Line 15:		Line 19:
	To make the tun module load on boot, use this command:		To make the tun module load on boot, use this command:
	{{Cmd\|# cat /etc/modules {{!}} grep tun {{!}}{{!}} echo tun >> /etc/modules}}		{{Cmd\|# cat /etc/modules {{!}} grep tun {{!}}{{!}} echo tun >> /etc/modules}}

	~~To make the libvirtd service start, run the following:~~
	~~{{Cmd\|# rc-service libvirtd start}}~~

	If you prefer bridging a guest over your Ethernet interface, you need to make a [[Bridge#Configuration_file\|bridge]].		If you prefer bridging a guest over your Ethernet interface, you need to make a [[Bridge#Configuration_file\|bridge]].

Sprungles: Describing how to start the libvirtd service.

2025-05-08T14:21:00Z

Describing how to start the libvirtd service.

← Older revision		Revision as of 14:21, 8 May 2025
Line 15:		Line 15:
	To make the tun module load on boot, use this command:		To make the tun module load on boot, use this command:
	{{Cmd\|# cat /etc/modules {{!}} grep tun {{!}}{{!}} echo tun >> /etc/modules}}		{{Cmd\|# cat /etc/modules {{!}} grep tun {{!}}{{!}} echo tun >> /etc/modules}}

			To make the libvirtd service start, run the following:
			{{Cmd\|# rc-service libvirtd start}}

	If you prefer bridging a guest over your Ethernet interface, you need to make a [[Bridge#Configuration_file\|bridge]].		If you prefer bridging a guest over your Ethernet interface, you need to make a [[Bridge#Configuration_file\|bridge]].

Kalts: /* Networking */

2024-11-16T14:01:12Z

Networking

← Older revision		Revision as of 14:01, 16 November 2024
Line 18:		Line 18:
	If you prefer bridging a guest over your Ethernet interface, you need to make a [[Bridge#Configuration_file\|bridge]].		If you prefer bridging a guest over your Ethernet interface, you need to make a [[Bridge#Configuration_file\|bridge]].

	It's quite common to use bridges with KVM environments. But when IPv6 is used, Alpine will assign itself a link-local address as well as an SLAAC address in case there's a router sending Router Advertisements. You don't want this because you don't want ~~to have~~ the KVM host an IP address in every network it serves to guests. Unfortunately IPv6 can not just be disabled for the bridge via a sysctl configuration file, because the bridge might not be up when the sysctl config is applied during boot. What works is to put a post-up hook into the /etc/network/interfaces file like this:		It's quite common to use bridges with KVM environments. But when IPv6 is used, Alpine will assign itself a link-local address as well as an SLAAC address in case there's a router sending Router Advertisements. You don't want this because you don't want the KVM host to have an IP address in every network it serves to guests. Unfortunately IPv6 can not just be disabled for the bridge via a sysctl configuration file, because the bridge might not be up when the sysctl config is applied during boot. What works is to put a post-up hook into the /etc/network/interfaces file like this:
	auto brlan		auto brlan
	iface brlan inet manual		iface brlan inet manual

Ncopa: /* Provision an Alpine Linux vm with virt-install */

2024-06-21T15:20:18Z

Provision an Alpine Linux vm with virt-install

← Older revision		Revision as of 15:20, 21 June 2024
Line 54:		Line 54:

	You can use {{Path\|virt-install}} to install Alpine in a VM. First create the {{ Path \| meta-data}} and {{Path \| user-data }} files.		You can use {{Path\|virt-install}} to install Alpine in a VM. First create the {{ Path \| meta-data}} and {{Path \| user-data }} files.
			{{Path\|meta-data}}:
			hostname: alpine-vm

			{{Path\|user-data}}:
	<pre>		<pre>
	#alpine-config		#alpine-config
Line 75:		Line 79:

	Then run:		Then run:
	{{Cmd \| <nowiki>virt-install --name ~~tmp~~-~~alp~~ \		{{Cmd \| <nowiki>virt-install --name alpine-vm \
	--disk size=4 \		--disk size=4 \
	--location $HOME/Downloads/alpine-virt-3.20.1-x86_64.iso,kernel=boot/vmlinuz-virt,initrd=boot/initramfs-virt \		--location $HOME/Downloads/alpine-virt-3.20.1-x86_64.iso,kernel=boot/vmlinuz-virt,initrd=boot/initramfs-virt \

Ncopa: /* Provision an Alpine Linux vm with virt-install */

2024-06-21T15:18:55Z

Provision an Alpine Linux vm with virt-install

← Older revision		Revision as of 15:18, 21 June 2024
Line 53:		Line 53:
	== Provision an Alpine Linux vm with virt-install ==		== Provision an Alpine Linux vm with virt-install ==

	You can use {{~~Cmd~~\|virt-install}} to install Alpine in a VM. First create the {{ Path \| meta-data}} and {{Path \| user-data }} files.		You can use {{Path\|virt-install}} to install Alpine in a VM. First create the {{ Path \| meta-data}} and {{Path \| user-data }} files.
	<pre>		<pre>
	#alpine-config		#alpine-config
Line 84:		Line 84:
	--cloud-init meta-data=meta-data,user-data=user-data		--cloud-init meta-data=meta-data,user-data=user-data
	</nowiki>}}		</nowiki>}}

	== Guest lifecycle management ==		== Guest lifecycle management ==
	The libvirt-guests service (available from Alpine 3.13.5) allows running guests to be automatically suspended or shut down when the host is shut down or rebooted.		The libvirt-guests service (available from Alpine 3.13.5) allows running guests to be automatically suspended or shut down when the host is shut down or rebooted.

Ncopa: add install alpine with virt-install

2024-06-21T15:18:10Z

add install alpine with virt-install

@@ Line 51: / Line 51: @@
 }}
 == Guest lifecycle management ==
 The libvirt-guests service (available from Alpine 3.13.5) allows running guests to be automatically suspended or shut down when the host is shut down or rebooted.

Sertonix: /* vfio */ link to udev/eudev article

2023-11-10T11:11:04Z

vfio: link to udev/eudev article

← Older revision		Revision as of 11:11, 10 November 2023
Line 113:		Line 113:
	[ 0.903768] DMAR: Intel(R) Virtualization Technology for Directed I/O		[ 0.903768] DMAR: Intel(R) Virtualization Technology for Directed I/O

	If you do not run libvirt VMs under ''root'' (''egrep '^#*user' /etc/libvirt/qemu.conf''), then you must have correct permission on ''/dev/vfio/<iommu_group>'', eg. ''/dev/vfio/12''. You have to tune ''/etc/mdev.conf'' or ~~UDEV~~ rules. Also note that if there are multiple PCI devices in the same iommu group, you always have to add all of them to the VM otherwise you'll get an error message like "Please ensure all devices within the iommu_group are bound to their vfio bus driver"		If you do not run libvirt VMs under ''root'' (''egrep '^#*user' /etc/libvirt/qemu.conf''), then you must have correct permission on ''/dev/vfio/<iommu_group>'', eg. ''/dev/vfio/12''. You have to tune ''/etc/mdev.conf'' or [[udev]] rules. Also note that if there are multiple PCI devices in the same iommu group, you always have to add all of them to the VM otherwise you'll get an error message like "Please ensure all devices within the iommu_group are bound to their vfio bus driver"

	# virsh dumpxml vm01 \| xmllint --xpath '//*/hostdev' -		# virsh dumpxml vm01 \| xmllint --xpath '//*/hostdev' -

Zcrayfish: Rescued a dead link.

2023-09-03T23:18:09Z

Rescued a dead link.

← Older revision		Revision as of 23:18, 3 September 2023
Line 93:		Line 93:
	# update-extlinux		# update-extlinux

	For GRUB (which [https://git.alpinelinux.org/aports/tree/main/grub/alpine-mkconfig.patch#n9 now also uses] the update-extlinux.conf if present), run:		For GRUB (which [https://web.archive.org/web/20220821140615/https://git.alpinelinux.org/aports/tree/main/grub/alpine-mkconfig.patch#n9 now also uses] the update-extlinux.conf if present), run:

	# grub-mkconfig -o /boot/grub/grub.cfg		# grub-mkconfig -o /boot/grub/grub.cfg

Faust: /* Networking */

2023-08-23T14:01:18Z

Networking

← Older revision		Revision as of 14:01, 23 August 2023
Line 9:		Line 9:
	By default, libvirt uses NAT for VM connectivity. If you want to use the default configuration, you need to load the tun module.		By default, libvirt uses NAT for VM connectivity. If you want to use the default configuration, you need to load the tun module.
	{{Cmd\|# modprobe tun}}		{{Cmd\|# modprobe tun}}
	{{Cmd\|~~add tun to autostart:~~ # echo "tun" >> /etc/modules-load.d/tun.conf}}
			Add tun to autostart:
			{{Cmd\|# echo "tun" >> /etc/modules-load.d/tun.conf}}

	To make the tun module load on boot, use this command:		To make the tun module load on boot, use this command: