KVM - Recent changes [en]

Special:Log/upload

2013-05-12T18:53:49Z

uploaded "[[Image:2012-forum Efficient Guest Agnostic Virtualization with Embedded Power Architecture KVM.pdf]]"

KVM Forum 2012

2013-05-12T18:43:21Z

lightning talks update

Revision as of 18:43, 12 May 2013		Current revision
Line 67:		Line 67:
	\|4:30pm \|\| [[Media:2012-forum-multiqueue-networking-for-kvm.pdf \| Multiqueue Networking for KVM]] \|\| Jason Wang, Red Hat \|\| [[Media:2012-forum-WHQLAndTheCommunity.pdf \| WHQL Pprocess for Windows Drivers and What the Community Can Learn From It]] \|\| Yan Vugenfirer, Daynix		\|4:30pm \|\| [[Media:2012-forum-multiqueue-networking-for-kvm.pdf \| Multiqueue Networking for KVM]] \|\| Jason Wang, Red Hat \|\| [[Media:2012-forum-WHQLAndTheCommunity.pdf \| WHQL Pprocess for Windows Drivers and What the Community Can Learn From It]] \|\| Yan Vugenfirer, Daynix
	\|-		\|-
-	\|5:00pm \|\| Lightning Talks: [[Media:2012-forum-Brugger-lightningtalk.pdf \| PV Disk I/O]] * [[Media:2012-forum-ovmf.pdf \| OVMF]] * [[Media:2012-forum NetWare as KVM Guest.pdf \| Netware as KVM Guest]] \|\| Matthias Brugger, Laszlo Ersek, Bruce Rogers \|\| \|\|	+	\|5:00pm \|\| Lightning Talks: [[Media:2012-forum-Brugger-lightningtalk.pdf \| PV Disk I/O]] * [[Media:2012-forum-ovmf.pdf \| OVMF]] * [[Media:2012-forum NetWare as KVM Guest.pdf \| Netware as KVM Guest]] * [[Media:2012-forum Efficient Guest Agnostic Virtualization with Embedded Power Architecture KVM.pdf \| Efficient Guest Agnostic Virtualization with Embedded Power Architecture KVM]] \|\| Matthias Brugger, Laszlo Ersek, Bruce Rogers, Varun Sethi \|\| \|\|
	\|}		\|}

KvmOnGentoo

2013-05-09T11:34:53Z

Revision as of 11:34, 9 May 2013		Current revision
Line 14:		Line 14:

	== Installing ==		== Installing ==
-	* printf '%s\n' 'QEMU_SOFTMMU_TARGETS="i386 x86_64"' 'QEMU_USER_TARGETS="i386 x86_64"' >> /etc/protage/make.conf	+	* printf '%s\n' 'QEMU_SOFTMMU_TARGETS="i386 x86_64"' 'QEMU_USER_TARGETS="i386 x86_64"' >> /etc/portage/make.conf
-	(If you haven't migrated /etc/make.conf to /etc/protage/make.conf yet, use /etc/portage instead or migrate it to /etc/protage/make.conf)	+	(If you haven't migrated /etc/make.conf to /etc/portage/make.conf yet, use /etc/make.conf instead or migrate it to /etc/portage/make.conf)
	* emerge app-emulation/qemu-kvm		* emerge app-emulation/qemu-kvm

HOWTO

2013-05-09T11:30:35Z

add link to gentoo wiki page, probably need to delete local KvmOnGentoo

Revision as of 11:30, 9 May 2013		Current revision
Line 52:		Line 52:

	=== Gentoo ===		=== Gentoo ===
		+	* Gentoo has [http://wiki.gentoo.org/wiki/QEMU good page about qemu/kvm in their wiki].
	* [[KvmOnGentoo\|KVM on Gentoo hosts]]		* [[KvmOnGentoo\|KVM on Gentoo hosts]]

KvmOnGentoo

2013-05-09T11:29:59Z

Revision as of 11:29, 9 May 2013		Current revision
Line 14:		Line 14:

	== Installing ==		== Installing ==
-	* printf '%s\n' 'QEMU_SOFTMMU_TARGETS="i386 x86_64"' 'QEMU_USER_TARGETS="i386 x86_64"' >> /etc/make.conf	+	* printf '%s\n' 'QEMU_SOFTMMU_TARGETS="i386 x86_64"' 'QEMU_USER_TARGETS="i386 x86_64"' >> /etc/protage/make.conf
		+	(If you haven't migrated /etc/make.conf to /etc/protage/make.conf yet, use /etc/portage instead or migrate it to /etc/protage/make.conf)
	* emerge app-emulation/qemu-kvm		* emerge app-emulation/qemu-kvm

Networking

2013-05-08T10:27:17Z

Added "Compatibility" part

Revision as of 10:27, 8 May 2013		Current revision
Line 18:		Line 18:

	'''Solution:'''		'''Solution:'''
-	* simply run your guest with "-net nic -net user", e-g:	+	* simply run your guest without specifying network parameters, which by default will create user-lever (a.k.a slirp) networking:
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic -net user	+	qemu-system-x86_64 -hda /path/to/hda.img

	'''Notes:'''		'''Notes:'''
	* The IP address can be automatically assigned to the guest thanks to the DHCP service integrated in QEMU		* The IP address can be automatically assigned to the guest thanks to the DHCP service integrated in QEMU
	* If you run multiple guests on the host, you don't need to specify a different MAC address for each guest		* If you run multiple guests on the host, you don't need to specify a different MAC address for each guest
-	* You can still access one specific port on the guest using the "hostfwd" option. This means e.g. if you want to transport a file with scp from host to guest, start the guest with "-net nic -net user,hostfwd=tcp::5555-:22". Now you are forwarding the host port 5555 to the guest port 22. After starting up the guest, you can transport a file with e.g. "scp -P 5555 file.txt root@localhost:/tmp" from host to guest. Or you can also use other address of the host to connect to.	+	* The default is equivalent to this explicit setup:
		+	qemu-system-x86_64 -hda /path/to/hda.img -netdev user,id=user.0 -device e1000,netdev=user.0
		+	* user.0 identifier above is just to connect the two halves into one, you may use any identifier you wish, such as "n" or "net0".
		+	* Use rtl8139 instead of e1000 to get 8139-series NIC.
		+	* You can still access one specific port on the guest using the "hostfwd" option. This means e.g. if you want to transport a file with scp from host to guest, start the guest with "-device e1000,netdev=user.0 -netdev user,id=user.0,hostfwd=tcp::5555-:22". Now you are forwarding the host port 5555 to the guest port 22. After starting up the guest, you can transport a file with e.g. "scp -P 5555 file.txt root@localhost:/tmp" from host to guest. Or you can also use other address of the host to connect to.


Line 68:		Line 72:

	* Run each guest with the following, replacing $macaddress with the value from the previous step		* Run each guest with the following, replacing $macaddress with the value from the previous step
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic,macaddr=$macaddress -net tap	+	qemu-system-x86_64 -hda /path/to/hda.img -device e1000,netdev=net0,mac=$macaddress -netdev tap,id=net0

	'''Notes:'''		'''Notes:'''
	* If you don't want to run as root, the qemu-ifup must be executable by the user you want to use		* If you don't want to run as root, the qemu-ifup must be executable by the user you want to use
	* You can either create a system-wide qemu-ifup in /etc/qemu-ifup or use another one. In the latter case, run		* You can either create a system-wide qemu-ifup in /etc/qemu-ifup or use another one. In the latter case, run
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic,macaddr=$macaddress -net tap,script=/path/to/qemu-ifup	+	qemu-system-x86_64 -hda /path/to/hda.img -device e1000,netdev=net0,mac=$macaddress -netdev tap,id=net0,script=/path/to/qemu-ifup

	* Each guest on the private virtual network must have a different MAC address		* Each guest on the private virtual network must have a different MAC address
Line 182:		Line 186:

	* Run each guest with the following, replacing $macaddress with the value from the previous step		* Run each guest with the following, replacing $macaddress with the value from the previous step
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic,macaddr=$macaddress -net tap	+	qemu-system-x86_64 -hda /path/to/hda.img -device e1000,netdev=net0,mac=$macaddress -netdev tap,id=net0

	'''Notes:'''		'''Notes:'''
	* If you don't want to run as root, the qemu-ifup must be executable by the user you want to use		* If you don't want to run as root, the qemu-ifup must be executable by the user you want to use
	* You can either create a system-wide qemu-ifup in /etc/qemu-ifup or use another one. In the latter case, run		* You can either create a system-wide qemu-ifup in /etc/qemu-ifup or use another one. In the latter case, run
-	qemu-system-x86_64 -hda /path/to/hda.img -net nic,macaddr=$macaddress -net tap,script=/path/to/qemu-ifup	+	qemu-system-x86_64 -hda /path/to/hda.img -device e1000,netdev=net0,mac=$macaddress -netdev tap,id=net0,script=/path/to/qemu-ifup

	* Each guest on the network must have a different MAC address		* Each guest on the network must have a different MAC address
Line 225:		Line 229:
	There's now a page dedicated to ideas for improving		There's now a page dedicated to ideas for improving
	[[Networking Performance]].		[[Networking Performance]].
		+
		+	== Compatibility ==
		+
		+	There's another, old and obsolete syntax of specifying network for virtual machines. Above examples uses -netdev..-device model, old way used -net..-net pairs. For example,
		+
		+	-netdev tap,id=net0 -device e1000,netdev=net0,mac=52:54:00:12:34:56
		+
		+	is about the same as old
		+
		+	-net tap,vlan=0 -net nic,vlan=0,model=e1000,macaddr=52:54:00:12:34:56
		+
		+	(note mac => macaddr parameter change as well; vlan=0 is the default).
		+
		+	Old way used the notion of "VLANs" - these are QEMU VLANS, which has nothing to do with 802.1q VLANs. Qemu VLANs are numbered starting with 0, and it's possible to connect one or more devices (either host side, like -net tap, or guest side, like -net nic) to each VLAN, and, in particular, it's possible to connect more than 2 devices to a VLAN. Each device in a VLAN gets all traffic received by every device in it. This model was very confusing for the user (especially when a guest has more than one NIC).
		+
		+	In new model, each host side correspond to just one guest side, forming a pair of devices based on -netdev id= and -device netdev= parameters. It is less confusing, it is faster (because it's always 1:1 pair), and it supports more parameters than old -net..-net way.
		+
		+	However, -net..-net is still supported, used widely, and mentioned in lots of various HOWTOs and guides around the world. It is also a bit shorter and so faster to type.

KVM Forum 2012

2013-05-07T05:53:33Z

Revision as of 05:53, 7 May 2013		Current revision
Line 87:		Line 87:

	Jeff Cody managed to get a photograph of (a large part of) the KVM / QEMU community development team. [http://www.linux-kvm.org/static/kvm-forum-2012-barcelona-team-photo.html View the photo and name key]		Jeff Cody managed to get a photograph of (a large part of) the KVM / QEMU community development team. [http://www.linux-kvm.org/static/kvm-forum-2012-barcelona-team-photo.html View the photo and name key]
		+
		+	== Notes ==
		+
		+	Some notes from the talks -- http://kashyapc.fedorapeople.org/virt/kvm-forum-2012-notes.txt

Main Page

2013-04-30T10:13:33Z

Revision as of 10:13, 30 April 2013		Current revision
Line 1:		Line 1:
	== Kernel Based Virtual Machine ==		== Kernel Based Virtual Machine ==

-	KVM (for Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V). It consists of a loadable kernel module, kvm.ko, that provides the core virtualization infrastructure and a processor specific module, kvm-intel.ko or kvm-amd.ko.	+	KVM (for Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V). It consists of a loadable kernel module, kvm.ko, that provides the core virtualization infrastructure and a processor specific module, kvm-intel.ko or kvm-amd.ko. KVM also requires a modified QEMU although work is underway to get the required changes upstream.

	Using KVM, one can run multiple virtual machines running unmodified Linux or Windows images. Each virtual machine has private virtualized hardware: a network card, disk, graphics adapter, etc.		Using KVM, one can run multiple virtual machines running unmodified Linux or Windows images. Each virtual machine has private virtualized hardware: a network card, disk, graphics adapter, etc.

	The kernel component of KVM is included in mainline Linux, as of 2.6.20.		The kernel component of KVM is included in mainline Linux, as of 2.6.20.
-
-	The userspace component of KVM is included in mainline QEMU, as of 1.3.

	KVM is open source software.		KVM is open source software.
Line 15:		Line 13:
	\|style="width:50%;border:none;"\|		\|style="width:50%;border:none;"\|
	* [[KVM Forum]]		* [[KVM Forum]]
-	** [[KVM Forum 2012]]
	** [[KVM Forum 2011]]		** [[KVM Forum 2011]]
	** [[KVM Forum 2010]]		** [[KVM Forum 2010]]
-	** [[KVM Forum 2008]]	+	* [[LinuxPlumbers2010\|Linux Plumbers Conference 2010]]
-	** [[KVM Forum 2007]]	+
-	* Linux Plumbers Conference	+
-	** [[LinuxPlumbers2010\|LPC 2010]]	+
-	** [[LPC 2012]]	+
	* [[TODO]]		* [[TODO]]
	* [[KVM-Autotest]]		* [[KVM-Autotest]]
Line 36:		Line 29:
	\|style="width:50%;border:none;"\|		\|style="width:50%;border:none;"\|
	* [http://www.qemu.org/ QEMU]		* [http://www.qemu.org/ QEMU]
		+	* [http://www.diamondlinks.net link building service]
		+	* [http://www.vinfotech.com/solutions/social-network-design.htm Social Network Design]
		+	* [http://www.vinfotech.com/solutions/startup-web-design.htm Startup Web Design]
		+	* [http://www.vinfotech.com/web_2.0/web_20_design.htm Web 2.0 Design]
		+	* [http://impact-resumes.net/services/career-change-resume.htm Career Change Resume]
	* [http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors Xen's HVM Compatible Processors List]		* [http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors Xen's HVM Compatible Processors List]
	\|style="width:50%;border:none;"\|		\|style="width:50%;border:none;"\|

Guest Support Status

2013-04-26T13:51:32Z

add Windows NT 4.0 SP6 + qemu-kvm 1.4.1 + vmmouse

Revision as of 13:51, 26 April 2013		Current revision
Line 375:		Line 375:
	\|-		\|-

		+	\| Windows NT 4.0 SP6
		+	\| 32
		+	\| qemu-kvm 1.4.1, 2.6.32
		+	\| Intel
		+	\| 64
		+	\| Works
		+	\| requires -cpu qemu32, install [https://packages.vmware.com/tools/esx/3.5latest/windows/x86/VMware-tools-windows-3.5.0-988599.iso vmmouse] driver instead of default ps/2 mouse, use Universal VBE30 for VGA (http://bearwindows.zcm.com.au/vbempg.zip)
		+	\|-

	\| Windows 95		\| Windows 95

WindowsGuestDrivers/Download Drivers

2013-04-22T22:06:59Z

Remove outdates 'notes' section

Revision as of 22:06, 22 April 2013		Current revision
Line 17:		Line 17:

	[http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/ Latest VirtIO drivers for Windows from Fedora ]		[http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/ Latest VirtIO drivers for Windows from Fedora ]
-
-	===Notes===
-	* as of this writing (2011-Nov-08), latest drivers are of version "15", dated "15-Jun-2011", with the CD image being virtio-win-0.1-mm34.iso. In that image, WindowsXP drivers does not seem to work, it is impossible to install them using regular winXP driver interface. But the previous drivers, version "14" as found on this [http://alt.fedoraproject.org/pub/alt/virtio-win/ Directory], dated "13-Jan-2011", from CD image named "virtio-win-1.1.16.iso", installs on winXP fine. (note: in my experience, the "15" drivers work just fine on XP, except the organization of the ISO is awful - the network driver is found in XP\x86 directory, while the storage, serial and balloon drivers are in WXp\x86 directory; drivers for other Windows versions are similarly scattered)
-	* 2011-12-21: Debian Lenny Server uses the quite outdated kvm-72. The current network drivers from RedHat/Fedora do not even install (tested on XP/2003) - using the "Windows-2" virtio drivers from [http://sourceforge.net/projects/kvm/files/kvm-guest-drivers-windows/2/ kvm-guest-drivers-2] is ok. The floppy disk image with the virtio-block driver (for F6 installation) provided by the Fedora Project (virtio-win-1.1.16) works with kvm-72, though.

	= Code signing drivers for the Windows 64bit platforms =		= Code signing drivers for the Windows 64bit platforms =

Code

2013-04-22T12:28:46Z

Revision as of 12:28, 22 April 2013		Current revision
Line 26:		Line 26:
	== userspace git tree ==		== userspace git tree ==

-	The kvm userspace code (libkvm and qemu) is available through a git tree. To create a repository using git, type	+	As of QEMU 1.3, the KVM userspace code is in mainline QEMU. Please use and develop with
		+
		+	git clone git://git.qemu-project.org/qemu.git
		+
		+	'''If you want to contribute code''', please see the [http://wiki.qemu.org/Contribute/StartHere guidelines] and submit patches to qemu-devel@nongnu.org.
		+
		+	The old qemu-kvm.git fork repository is still available but outdated, type

	git clone git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git		git clone git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
Line 32:		Line 38:
	Alternatively, it is also accessible through the kernel.org gitweb interface:		Alternatively, it is also accessible through the kernel.org gitweb interface:
	[http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=summary]		[http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=summary]
-
-	'''If you want to contribute code''', please [http://wiki.qemu.org/Contribute/StartHere develop against qemu.git] and submit patches to qemu-devel@nongnu.org. The qemu-kvm.git tree regularly gets changes from qemu.git and patches against qemu-kvm.git should be minimized.

Status

2013-04-22T12:20:55Z

Revision as of 12:20, 22 April 2013		Current revision
Line 2:		Line 2:

	KVM is included in the mainline linux kernel since 2.6.20 and is stable and fast for most workloads.		KVM is included in the mainline linux kernel since 2.6.20 and is stable and fast for most workloads.
		+
		+	The userspace tools are part of mainline QEMU since 1.3.

	It is also available as a patch for recent Linux kernel versions and as an external module that can be used with your favorite distro- provided kernel going back up to 2.6.16, therefore including all latest versions for Enterprise Linux Distributions.		It is also available as a patch for recent Linux kernel versions and as an external module that can be used with your favorite distro- provided kernel going back up to 2.6.16, therefore including all latest versions for Enterprise Linux Distributions.

Downloads

2013-04-22T12:19:56Z

Revision as of 12:19, 22 April 2013		Current revision
Line 1:		Line 1:
	=Downloads=		=Downloads=
-
-	(If you are searching the latest Windows drivers, go [[http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers here]])

	Most Linux distros already have KVM kernel modules and userspace tools available through their packaging systems. This is the easiest and recommended way of using KVM.		Most Linux distros already have KVM kernel modules and userspace tools available through their packaging systems. This is the easiest and recommended way of using KVM.

-	If you want to use the latest version of KVM kernel modules and supporting userspace, you can download the latest version from [http://sourceforge.net/project/showfiles.php?group_id=180599 http://sourceforge.net/project/showfiles.php?group_id=180599].	+	* <b>KVM kernel modules</b> are part of the Linux kernel package
		+	* <b>Userspace tools</b> are usually called "qemu-kvm" or "kvm"
		+	* <b>Linux guest drivers</b> are part of the Linux kernel package
		+	* <b>Windows guest drivers</b> are available [http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers here]
		+
		+	Please try your distro's packages first. Normally you do not need to patch anything or build from source.
		+
		+	===Getting old versions of KVM===
		+
		+	If you want to use specific versions of KVM kernel modules and supporting userspace, you can download the latest version from [http://sourceforge.net/project/showfiles.php?group_id=180599 http://sourceforge.net/project/showfiles.php?group_id=180599]. Note that as of QEMU 1.3, the userspace code comes straight from [http://wiki.qemu.org/Download http://wiki.qemu.org/Download].

	For the userspace components, you will find both qemu-kvm-<version> and kvm-<version> there.		For the userspace components, you will find both qemu-kvm-<version> and kvm-<version> there.

Main Page

2013-04-22T12:06:59Z

Revision as of 12:06, 22 April 2013		Current revision
Line 6:		Line 6:

	The kernel component of KVM is included in mainline Linux, as of 2.6.20.		The kernel component of KVM is included in mainline Linux, as of 2.6.20.
		+
		+	The userspace component of KVM is included in mainline QEMU, as of 1.3.

	KVM is open source software.		KVM is open source software.