RunningKVM

2009-05-31T03:23:59Z

ShengYang: add libpci-dev to required list, for device assignment

== Prerequisites ==

You will need (see download section):

* kvm-''release''.tar.gz
* A VT capable Intel processor, or an SVM capable AMD processor
* qemu prerequisites:
** `zlib` libraries and headers
** `SDL` libraries and headers
** `alsa` libraries and headers (optional alsa support: disabled by default but can be enabled with --enable-alsa)
** `gnutls` libraries and headers (optional VNC TLS support: enabled by default but can be disabled with --disable-vnc-tls)
** kernel headers (on Fedora, the kernel-devel package)

On a debian etch system you can install the prerequisites with:
apt-get install gcc libsdl1.2-dev zlib1g-dev libasound2-dev linux-kernel-headers pkg-config libgnutls-dev libpci-dev

'''Note:''' When building from git, you also need gawk.

Please report problems (and successes) to the [[Lists,_IRC| mailing list]].

== Unpacking and configuring kvm components ==

You may wish to take a look at the ["Kernel-optimizations"] page.
There exists a [attachment:kvm-26-alt-grab.diff.gz patch] which will change the SDL keygrab combination from ctrl-alt to ctrl-alt-shift. It was written primarily to deal with the heavy use of ctrl-alt-delete in NT-based VMs.

If you are using a patched kernel (e.g. a recent -mm kernel or the kvm git tree), configure the kernel normally, boot into it, and:

tar xzf kvm-release.tar.gz
cd kvm-release
./configure --prefix=/usr/local/kvm --with-patched-kernel
make
sudo make install
sudo /sbin/modprobe kvm-intel
# or: sudo /sbin/modprobe kvm-amd

If you're ''not'' running a patched kernel:

tar xzf kvm-release.tar.gz
cd kvm-release
./configure --prefix=/usr/local/kvm
make
sudo make install
sudo /sbin/modprobe kvm-intel
# or: sudo /sbin/modprobe kvm-amd

'''Note:''' if sound doesn't play in the guest vm you can add --audio-drv-list="alsa oss" to ./configure as explained in http://www.linux-kvm.com/content/sound-problem-solved

== Creating a disk image for the guest ==
/usr/local/kvm/bin/qemu-img create -f qcow vdisk.img 10G

== Installing a guest operating system ==

sudo /usr/local/kvm/bin/qemu-system-x86_64 -hda vdisk.img -cdrom /path/to/boot-media.iso \
-boot d -m 384

(kvm doesn't make a distinction between i386 and x86_64 so even in i386 you should use `qemu-system-x86_64`)[[BR]]

If you have less than 1GB of memory don't use the -m 384 flag (which allocates 384 MB of RAM for the guest). For computers with 512MB of RAM it's safe to use -m 192, or even -m 128 (the default)

== Running the newly-installed guest ==
sudo /usr/local/kvm/bin/qemu-system-x86_64 vdisk.img -m 384

or a slightly more complicated example, where it is assumed that bridged networking is available on tap0; see ["Kernel-optimizations"] for some setup hints:

/usr/local/kvm/bin/qemu-system-x86_64 -hda xp-curr.img -m 512 -soundhw es1370 -no-acpi -snapshot -localtime -boot c -usb -usbdevice tablet -net nic,vlan=0,macaddr=00:00:10:52:37:48 -net tap,vlan=0,ifname=tap0,script=no

(kvm doesn't make a distinction between i386 and x86_64 so even in i386 you should use `qemu-system-x86_64`)

If you're on Debian Etch, substitute `kvm` for `qemu-system-x86_64` (thanks to fromport, soren and mael_). See also the entries under the label "Ubuntu" on the [[HOWTO]] page.
qemu-system-x86_64`

If you're on Fedora/RHEL/CentOS (and installed a kvm package and not built kvm yourself from source) then substitute '''qemu-kvm''' for '''qemu-system-x86_64'''

KVM Forum 2008

2008-06-18T08:07:30Z

ShengYang: My boss Xin is not there...

= Information on the recently-concluded KVM Forum 2008 =

==== Wednesday June 11th ====
{| border="1" cellpadding="2" cellspacing="0"
| Session Topic
| Speaker
|
|-
| [attachment:kdf2008_1.pdf Keynote]
| Avi Kivity, Qumranet
|
|-
| [attachment:kdf2008_2.pdf Cross platform guest support]
| Paul Knowles, Transitive
|
|-
| [attachment:kdf2008_3.pdf KVM in Solid ICE]
| Dor Laor, Qumranet
|
|-
| [attachment:kdf2008_4.pdf Buiding a better Userspace - The current and future state of QEMU and KVM integration]
| Anthony Liguori, IBM
|
|-
| [attachment:kdf2008_5.pdf Mixing Xen and KVM: Xenner]
| Gerd Hoffman, Red Hat
|
|-
| [attachment:kdf2008_6.pdf KVM Limits - Arbitrary or Architectual?]
| Ryan Harper, Karl Rister, IBM
|
|-
| [attachment:kdf2008_7.pdf VMDq and SR-IOV support in KVM]
| Eddie Dong, Intel
|
|}

==== Thursday June 12th ====
{| border="1" cellpadding="2" cellspacing="0"
| Session Topic
| Speaker
|
|-
| [attachment:kdf2008_8.pdf Mac OS X in KVM]
| Alexander Graf, Novell
|
|-
| [attachment:kdf2008_9.pdf Beyond kvm.ko]
| Avi Kivity, Qumranet
|
|-
| [attachment:kdf2008_10.pdf State of KVM in PowerPC]
| Christian Ehrhardt, IBM
|
|-
| [attachment:kdf2008_11.pdf Accelerating KVM with hardware technology]
| Sheng Yang, Intel
|
|-
| [attachment:kdf2008_12.pdf Increasing Virtual Machine density with KSM]
| Izik Eidus, Qumranet
|
|-
| [attachment:kdf2008_13.pdf Shadow TLB management]
| Hollis Blanchard, IBM
|
|-
| [attachment:kdf2008_14.pdf Passthrough device access for KVM]
| Amit Shah, Qumranet & Allan Kay, Intel
|
|-
| [attachment:kdf2008_15.pdf Integrating KVM with the Linux memory management]
| Andrea Arcangeli, Qumranet
|
|-
| [attachment:kdf2008_16.pdf Paravirtualized file systems]
| Eric Van Hensbergen, IBM research
|
|}

==== Friday June 13th ====
{| border="1" cellpadding="2" cellspacing="0"
| Session Topic
| Speaker
|
|-
| [attachment:kdf2008_17.pdf KVM on Big Iron: Where to go from here?]
| Carsten Otte, IBM
|
|-
| [attachment:kdf2008_18.pdf Enabling KVM on IA64 system]
| Eddie Dong, Intel
|
|-
| [attachment:kdf2008_19.pdf Open-OVF: an OSS project around the Open Virtual Appliance format]
| Hollis Blanchard, IBM
|
|-
| [attachment:kdf2008_20.pdf Mini VM - Extending KVM towards Embedded systems]
| Jun Nakajima, Intel
|
|-
| [attachment:kdf2008_21.pdf Nested paging hardware and software]
| Ben Serebrin & Joerg Roedel, AMD
|
|-
| Concluding keynote
| Benny Schnaider, Qumranet
|

__NOTOC__

KVM - User contributions [en]

RunningKVM

KVM Forum 2008