Virtualization with KVM - Revision history

Mihai Prica: /* How to integrate with Poky */

2012-12-11T13:57:13Z

How to integrate with Poky

← Older revision		Revision as of 13:57, 11 December 2012
Line 19:		Line 19:

	== How to integrate with Poky ==		== How to integrate with Poky ==
	The meta-virtualization layer can be found on the official yocto source repositories page at [http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/ meta-virtualization]. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image. To obtain an KVM controller you have to build the '''kvm-image-minimal''' target.		The meta-virtualization layer can be found on the official yocto source repositories page at [http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/ meta-virtualization]. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image.
			To obtain an KVM controller you have to build the '''kvm-image-minimal''' target.

	== Virtual Machine Management ==		== Virtual Machine Management ==

Mihai Prica: /* How to integrate with Poky */

2012-12-11T13:55:57Z

How to integrate with Poky

← Older revision		Revision as of 13:55, 11 December 2012
Line 19:		Line 19:

	== How to integrate with Poky ==		== How to integrate with Poky ==
	The meta-virtualization layer can be found on the official yocto source repositories page, [http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/ meta-virtualization]. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image. To obtain an KVM controller you have to build the '''kvm-image-minimal''' target.		The meta-virtualization layer can be found on the official yocto source repositories page at [http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/ meta-virtualization]. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image. To obtain an KVM controller you have to build the '''kvm-image-minimal''' target.

	== Virtual Machine Management ==		== Virtual Machine Management ==

Mihai Prica: /* How to integrate with Poky */

2012-12-11T13:55:43Z

How to integrate with Poky

← Older revision		Revision as of 13:55, 11 December 2012
Line 19:		Line 19:

	== How to integrate with Poky ==		== How to integrate with Poky ==
	The meta-virtualization layer can be found on the official yocto source repositories page, [[http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/ meta-virtualization]]. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image. To obtain an KVM controller you have to build the '''kvm-image-minimal''' target.		The meta-virtualization layer can be found on the official yocto source repositories page, [http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/ meta-virtualization]. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image. To obtain an KVM controller you have to build the '''kvm-image-minimal''' target.

	== Virtual Machine Management ==		== Virtual Machine Management ==

Mihai Prica at 13:54, 11 December 2012

2012-12-11T13:54:28Z

← Older revision		Revision as of 13:54, 11 December 2012
Line 1:		Line 1:
	__NOTOC__		__NOTOC__

	Virtualization is a hot topic in the operating systems world these days. The use cases vary from server consolidation, virtual test environments to Linux enthusiasts who can’t decide which distribution is best. The Kernel-based Virtual Machine, [http://www.linux-kvm.org kvm] is a popular full-virtualization solution for Linux based systems. It can be used to run guests systems on ~~systems~~ with hardware virtualization extensions (AMD-V or Intel VT-x).		Virtualization is a hot topic in the operating systems world these days. The use cases vary from server consolidation, virtual test environments to Linux enthusiasts who can’t decide which distribution is best. The Kernel-based Virtual Machine, [http://www.linux-kvm.org kvm] is a popular full-virtualization solution for Linux based systems. It can be used to run guests systems on hosts with hardware virtualization extensions (AMD-V or Intel VT-x).
	The goal of this project was creating a minimal solution that would allow a user to run virtual machines (VM) using Poky from the Yocto Project. KVM was choosen as the virtualization solution because of the strong community support it enjoys and for the easy integration.		The goal of this project was creating a minimal solution that would allow a user to run virtual machines (VM) using Poky from the Yocto Project. KVM was choosen as the virtualization solution because of the strong community support it enjoys and for the easy integration.
	[[File:Yocto-KVM running multiple guests.png\|thumb\|upright=1.8\|Multiple guest running in the Yocto Project KVM host layer]]		[[File:Yocto-KVM running multiple guests.png\|thumb\|upright=1.8\|Multiple guest running in the Yocto Project KVM host layer]]

	== Packages ==		== Packages ==
	The project is ~~based on~~ the ~~meta-xen layer from~~ [http://~~www~~.~~openembedded~~.org/~~wiki~~/~~LayerIndex oe~~-~~core~~]. This layer ~~creates a target image that can act as a host~~ for ~~running multiple guest operating systems~~ using the Xen ~~hypervisor~~. It also features recipes for the libvirt package and for ~~most of its dependencies~~. There are a number of other dependencies that come from the meta-oe layer of oe-core.		The project is part of the [http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/ meta-virtualization] layer. This layer contains all the necessary recipes for creating VM controllers using the Xen, LXC and KVM hypervisors. It also features recipes for the libvirt package and other tools that can be used for the virtual machine management. There are a number of other dependencies that come from the meta-oe layer of oe-core.

	=== KVM ===		=== KVM ===
	KVM can be used to run multiple virtual machines that contain unmodified Windows or Linux images. The kvm component is included in the mainline Linux kernel starting from version 2.6.20. Since yocto uses 3.4.11 or a newer version of the Linux kernel, no extra packages are required only a proper kernel configuration.		KVM can be used to run multiple virtual machines that contain unmodified Windows or Linux images. The kvm component is included in the mainline Linux kernel starting from version 2.6.20. Since yocto uses 3.4.20 or a newer version of the Linux kernel, no extra packages are required only a proper kernel configuration.

	=== QEMU ===		=== QEMU ===
Line 19:		Line 19:

	== How to integrate with Poky ==		== How to integrate with Poky ==
	The meta-~~kvm~~ layer can be found at the [http://git.yoctoproject.org/cgit/cgit.cgi~~/poky-contrib/log/?h=mihaip~~/meta-~~kvm poky-contrib/mihaip~~/meta-~~kvm~~] ~~branch~~. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image.		The meta-virtualization layer can be found on the official yocto source repositories page, [[http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/ meta-virtualization]]. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image. To obtain an KVM controller you have to build the '''kvm-image-minimal''' target.

	== Virtual Machine Management ==		== Virtual Machine Management ==

Mihai Prica at 07:54, 3 December 2012

2012-12-03T07:54:42Z

← Older revision		Revision as of 07:54, 3 December 2012
Line 1:		Line 1:
	__NOTOC__		__NOTOC__

	Virtualization is a hot topic in the operating systems world these days. The use cases vary from server consolidation, virtual test environments to Linux ~~enthusiasms~~ who can’t decide which distribution is best. The Kernel-based Virtual Machine, [http://www.linux-kvm.org kvm] is a popular full-virtualization solution for Linux based systems. It can be used to run guests systems on systems with hardware virtualization extensions (AMD-V or Intel VT-x).		Virtualization is a hot topic in the operating systems world these days. The use cases vary from server consolidation, virtual test environments to Linux enthusiasts who can’t decide which distribution is best. The Kernel-based Virtual Machine, [http://www.linux-kvm.org kvm] is a popular full-virtualization solution for Linux based systems. It can be used to run guests systems on systems with hardware virtualization extensions (AMD-V or Intel VT-x).
	The goal of this project was creating a minimal solution that would allow a user to run virtual machines (VM) using Poky from the Yocto Project. KVM was choosen as the virtualization solution because of the strong community support it enjoys and for the easy integration.		The goal of this project was creating a minimal solution that would allow a user to run virtual machines (VM) using Poky from the Yocto Project. KVM was choosen as the virtualization solution because of the strong community support it enjoys and for the easy integration.
	[[File:Yocto-KVM running multiple guests.png\|thumb\|upright=1.8\|Multiple guest running in the Yocto Project KVM host layer]]		[[File:Yocto-KVM running multiple guests.png\|thumb\|upright=1.8\|Multiple guest running in the Yocto Project KVM host layer]]

Mihai Prica: /* CLI */

2012-12-03T07:53:00Z

CLI

← Older revision		Revision as of 07:53, 3 December 2012
Line 23:		Line 23:
	== Virtual Machine Management ==		== Virtual Machine Management ==
	=== CLI ===		=== CLI ===
	If you already have an existing KVM image(the disk image and optionally the kernel image), it can run it from the CLI using the various qemu-system-* commands depending on the desired guest architecture. To connect to the console of the VM, the user has to configure a vncserver to start on the guest. The '''vnc''' option can be used for this.<br/>		If you already have an existing KVM image(the disk image and optionally the kernel image), you can run it from the CLI using the various qemu-system-* commands depending on the desired guest architecture. To connect to the console of the VM, the user has to configure a vncserver to start on the guest. The '''vnc''' option can be used for this.<br/>
	Virsh is a powerful tool that can be used to create and manage VMs. It has a quite complicated syntax and it's not used directly in general.		Virsh is a powerful tool that can be used to create and manage VMs. It has a quite complicated syntax and it's not used directly in general.
	The target image does not contain any additional tools for the creation and the management of the virtual machines, but the libvirtd daemon is configured to listen for new connections. This allows other tools like virt-install to remotely connect to the hypervisor running on the system and run all the commands on the host.		The target image does not contain any additional tools for the creation and the management of the virtual machines, but the libvirtd daemon is configured to listen for new connections. This allows other tools like virt-install to remotely connect to the hypervisor running on the system and run all the commands on the host.

SaulWold: /* How to integrate with Poky */

2012-11-28T17:24:52Z

How to integrate with Poky

← Older revision		Revision as of 17:24, 28 November 2012
Line 19:		Line 19:

	== How to integrate with Poky ==		== How to integrate with Poky ==
	The meta-kvm layer can be found at [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=mihaip/meta-kvm poky-contrib/mihaip/meta-kvm]~~, on the mihaip/meta-kvm~~ branch. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image.		The meta-kvm layer can be found at the [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=mihaip/meta-kvm poky-contrib/mihaip/meta-kvm] branch. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image.

	== Virtual Machine Management ==		== Virtual Machine Management ==

SaulWold: /* How to integrate with Poky */

2012-11-28T17:24:18Z

How to integrate with Poky

← Older revision		Revision as of 17:24, 28 November 2012
Line 19:		Line 19:

	== How to integrate with Poky ==		== How to integrate with Poky ==
	The meta-kvm layer can be found at [~~git~~://git.yoctoproject.org/poky-contrib poky-contrib], on the mihaip/meta-kvm branch. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image.		The meta-kvm layer can be found at [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=mihaip/meta-kvm poky-contrib/mihaip/meta-kvm], on the mihaip/meta-kvm branch. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image.

	== Virtual Machine Management ==		== Virtual Machine Management ==

Mihai Prica at 10:58, 28 November 2012

2012-11-28T10:58:07Z

← Older revision		Revision as of 10:58, 28 November 2012
Line 19:		Line 19:

	== How to integrate with Poky ==		== How to integrate with Poky ==
	The meta-kvm layer can be found at ~~TODO~~. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image.		The meta-kvm layer can be found at [git://git.yoctoproject.org/poky-contrib poky-contrib], on the mihaip/meta-kvm branch. This layer contains a README that presents all the layer dependencies and the necessary steps to build the target image.

	== Virtual Machine Management ==		== Virtual Machine Management ==

Mihai Prica at 07:50, 26 November 2012

2012-11-26T07:50:03Z

← Older revision		Revision as of 07:50, 26 November 2012
Line 86:		Line 86:
	----		----
	'''Create image from configuration file'''<br/>		'''Create image from configuration file'''<br/>
	The images created with virt-manager are saved as xml files in <tt>/etc/libvirt/qemu</tt>. An example ~~of such a~~ configuration ~~file for a~~ virtual appliance with graphical interface ~~can be found '''TODO'''~~[[~~Media~~:~~Example~~.~~ogg here~~]] ~~and for an image~~ with no graphical interface ~~[[Media:Example.ogg here]] '''TODO'''.<br/>~~		The images created with virt-manager are saved as xml files in <tt>/etc/libvirt/qemu</tt>. You can find some example configuration files here:
	To ~~create a VM the following~~ steps ~~have to be followed~~:		* [[File:YoctoGUI.xml]] : virtual appliance with graphical interface;
	~~# Download~~ the ~~configuration~~ file.		* [[File:YoctoCLI.xml]] : virtual appliance with no graphical interface;
	~~# The~~ paths for the kernel and disk image ~~have been~~ marked with '''TODO'''~~. Change them to~~ the actual locations of the images on the host filesystem.		To use these files follow these steps:
	~~# Run~~		* download the file;
			* change the paths for the kernel and disk image that are marked with '''TODO''' with the actual locations of the images on the host filesystem.
			* run
	virsh [--conect REMOTE_URI] create config_file.xml		virsh [--conect REMOTE_URI] create config_file.xml