KVM - Revision history

46.59.61.80: Changed qemu-kvm to qemu (http://forums.funtoo.org/viewtopic.php?id=1657)

2013-04-23T18:31:20Z

Changed qemu-kvm to qemu (http://forums.funtoo.org/viewtopic.php?id=1657)

Drobbins at 19:06, 22 October 2012

2012-10-22T19:06:29Z

Setsuna-xero: /* Starting your first KVM virtual machine */

2012-10-01T20:20:30Z

‎Starting your first KVM virtual machine

Setsuna-xero: /* Tweaking KVM */

2012-10-01T20:18:32Z

‎Tweaking KVM

Setsuna-xero: /* Networking Options */

2012-09-30T21:45:09Z

‎Networking Options

Drobbins: /* Networking Options */

2012-09-09T20:42:25Z

‎Networking Options

Drobbins: /* Networking Options */

2012-09-09T20:41:01Z

‎Networking Options

Drobbins: /* Starting your first KVM virtual machine */

2012-09-09T20:40:18Z

‎Starting your first KVM virtual machine

Drobbins: /* Starting your first KVM virtual machine */

2012-09-09T20:36:40Z

‎Starting your first KVM virtual machine

Drobbins at 15:58, 29 April 2012

2012-04-29T15:58:13Z

@@ Line 23: / Line 23: @@
 </pre>
-Once the <tt>make.conf</tt> variables above are set, emerge qemu-kvm:
+Once the <tt>make.conf</tt> variables above are set, emerge qemu:
 <console>
-# ##i## emerge qemu-kvm
+# ##i## emerge qemu
 </console>

@@ Line 43: / Line 43: @@
 <console>
 # ##i##qemu-img create -f qcow2 vdisk.qcow2 10
-# ##i##qemu-kvm vdisk.qcow2 -m 1024 -cdrom systemrescuecd.iso  -vnc 127.0.0.1:1 -cpu host -net nic -net user
+# ##i##qemu-system-x86_64 vdisk.qcow2 -m 1024 -cdrom systemrescuecd.iso  -vnc 127.0.0.1:1 -cpu host -net nic -net user
 VNC server running on `127.0.0.1:5900'
 </console>
@@ Line 51: / Line 51: @@
 == Networking Options ==
-Above, networking will be enabled but will be on its own private LAN, and ping will not work. If you have a local bridge that you use for networking, the following steps will allow you use your existing bridge to provide higher-performance and full-featured network access to your virtual machine. Please see read [[Funtoo_Linux_Networking#Bridge_Configuration]] on how to configure a bridge
+Above, networking will be enabled but will be on its own private LAN, and ping will not work. If you have a local bridge that you use for networking, the following steps will allow you use your existing bridge to provide higher-performance and full-featured network access to your virtual machine.
-First, create your bridge and add a tap interface as a slave, make sure your user or group matches what you put in the template, Group is recomended over user for KVM.
+First, create <tt>/etc/qemu-ifup</tt> and add the following to it. Replace <tt>brlan</tt> with the name of your bridge:
-You should have a bridge configuration something like this.
+<syntaxhighlight lang="bash">
-<console>
+#!/bin/bash
-# brctl show
+ifconfig $1 0.0.0.0 promisc up
-bridge name     bridge id               STP enabled     interfaces
+brctl addif brlan $1
-br0             8000.00248c52ddc9       yes             eth1
+sleep 2
-                                                        tap0
+</syntaxhighlight>
-</console>
+Make it executable:
-To have kvm use the tap0 interface start the virtual machine as follows:
 <console>
-# ##i##qemu-kvm vdisk.qcow2 -m 1024 -cdrom systemrescuecd-x86-2.8.0.iso -cpu host -vnc 127.0.0.1:1 \
+# ##i##chmod +x /etc/qemu-ifup
--net nic -net tap,ifname=tap0,script=no,downscript=no
 </console>
+Start the virtual machine as follows:
-−
-To enable the higher performance Virto network driver use the following method
 <console>
-# ##i##qemu-kvm vdisk.qcow2 -m 1024 -cdrom systemrescuecd-x86-2.8.0.iso -cpu host -vnc 127.0.0.1:1 \
+# ##i##qemu-system-x86_64 vdisk.qcow2 -m 1024 -cdrom systemrescuecd-x86-2.8.0.iso -cpu host -vnc 127.0.0.1:1 -net nic -net tap,id=foo
--net nic,model=virtio,macaddr=10:22:33:44:51:66 -net tap,ifname=tap0,script=no,downscript=no
 </console>
 == Tweaking KVM ==
 === VNC Output ===

@@ Line 43: / Line 43: @@
 <console>
 # ##i##qemu-img create -f qcow2 vdisk.qcow2 10
-# ##i##qemu-system-x86_64 vdisk.qcow2 -m 1024 -cdrom systemrescuecd.iso  -vnc 127.0.0.1:1 -cpu host -net nic -net user
+# ##i##qemu-kvm vdisk.qcow2 -m 1024 -cdrom systemrescuecd.iso  -vnc 127.0.0.1:1 -cpu host -net nic -net user
 VNC server running on `127.0.0.1:5900'
 </console>

← Older revision		Revision as of 20:18, 1 October 2012
Line 88:		Line 88:

	== Tweaking KVM ==		== Tweaking KVM ==
		+
		+	=== Virtio Disks ===
		+
		+	If you want to enable the higher performance virtio block driver, you will need to use the following switch
		+	<console>
		+	-drive file=/vm.img,if=virtio
		+	</console>
		+	;Note
		+	:This requires kernel modules for the guest and host
		+	:Windows guest support is spotty, drivers can be acquired at the linux-kvm site [http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers]

	=== VNC Output ===		=== VNC Output ===

@@ Line 51: / Line 51: @@
 == Networking Options ==
-Above, networking will be enabled but will be on its own private LAN, and ping will not work. If you have a local bridge that you use for networking, the following steps will allow you use your existing bridge to provide higher-performance and full-featured network access to your virtual machine.
+Above, networking will be enabled but will be on its own private LAN, and ping will not work. If you have a local bridge that you use for networking, the following steps will allow you use your existing bridge to provide higher-performance and full-featured network access to your virtual machine. Please see read [[Funtoo_Linux_Networking#Bridge_Configuration]] on how to configure a bridge
-First, create <tt>/etc/qemu-ifup</tt> and add the following to it. Replace <tt>brlan</tt> with the name of your bridge:
+First, create your bridge and add a tap interface as a slave, make sure your user or group matches what you put in the template, Group is recomended over user for KVM.
-<syntaxhighlight lang="bash">
+You should have a bridge configuration something like this.
-#!/bin/bash
+<console>
-ifconfig $1 0.0.0.0 promisc up
+# brctl show
-brctl addif brlan $1
+bridge name     bridge id               STP enabled     interfaces
-sleep 2
+br0             8000.00248c52ddc9       yes             eth1
-</syntaxhighlight>
+                                                        tap0
-Make it executable:
 <console>
-# ##i##chmod +x /etc/qemu-ifup
+# ##i##qemu-kvm vdisk.qcow2 -m 1024 -cdrom systemrescuecd-x86-2.8.0.iso -cpu host -vnc 127.0.0.1:1 \
 </console>
-Start the virtual machine as follows:
 <console>
-# ##i##qemu-system-x86_64 vdisk.qcow2 -m 1024 -cdrom systemrescuecd-x86-2.8.0.iso -cpu host -vnc 127.0.0.1:1 -net nic -net tap,id=foo
+# ##i##qemu-kvm vdisk.qcow2 -m 1024 -cdrom systemrescuecd-x86-2.8.0.iso -cpu host -vnc 127.0.0.1:1 \
 </console>
 == Tweaking KVM ==

@@ Line 53: / Line 53: @@
 Above, networking will be enabled but will be on its own private LAN. If you have a local bridge that you use for networking, the following steps will allow you use your existing bridge to provide network access to your virtual machine.
-First, create <tt>/etc/qemu-ifup</tt> and add the following to it:
+First, create <tt>/etc/qemu-ifup</tt> and add the following to it. Replace <tt>brlan</tt> with the name of your bridge:
 <syntaxhighlight lang="bash">

← Older revision		Revision as of 15:58, 29 April 2012
Line 1:		Line 1:

−	== ~~Kernel Setup~~ ==	+	== Introduction ==

	KVM is a hardware-accelerated full-machine hypervisor and virtualization solution included as part of kernel 2.6.20 and later. It allows you to create and start hardware-accelerated virtual machines under Linux using the QEMU tools.		KVM is a hardware-accelerated full-machine hypervisor and virtualization solution included as part of kernel 2.6.20 and later. It allows you to create and start hardware-accelerated virtual machines under Linux using the QEMU tools.