View source for Local testing with KVM, VDE and dnsmasq

== Motivation ==

Imagine you already have a production infrastructure using FAI. You keep your config space in revision control and the production servers only have read-only access to the repository. Of course, you don't want to clog up the changelog with lots of revisions while testing changes. And of course, if you deploy a not perfectly tested change on your production infrastructure, and a colleague installs a server just at that moment, bad things can happen.

Or maybe you just can't be bothered to test everything on real servers. After all, they can be pretty slow to boot up with hardware RAID controllers, remote access cards and the like all needing to be initialized.

Or maybe you want to be able to work on your FAI configuration on your laptop while on the train, with no ready access to your regular DHCP and TFTP infrastructure.

In such cases, you would like to be able to work on your FAI configuration without leaving the comfort of your own workstation. And since even laptops are equipped with insane amounts of RAM nowadays, virtualization is an obvious solution.

== Goal ==

This Howto is written for Debian Lenny. It will show you how to install a [[http://www.linux-kvm.org/page/Main_Page KVM]] virtual machine via PXE, connected to your workstation via [[http://wiki.virtualsquare.org/index.php/VDE VDE]], with [[http://www.thekelleys.org.uk/dnsmasq/doc.html dnsmasq]] providing DHCP and TFTP services.

Please note that KVM is not a very good option if you have an old CPU with no virtualization extensions. Check your <tt>/proc/cpuinfo</tt> for the <tt>vmx</tt> or <tt>svm</tt> flag.