Previously when I needed to run Windows for testing or development at work I would run Windows under VMware. This was great and VMware is truly an amazing ground breaking piece of software. Even the model of providing VMware Player, and VMware server for free are brilliant business and marketing decisions.
All that aside I have been experimenting with the Open Source vitrualisation technologies quite a bit lately. For personal (desktop and laptop) vitrtualised services, testing anf development I have found KVM to be more than adequate. Recently I have moved my own PmWiki, Drupal, and other development websites and databases into one KVM machine and also started using another Windows KVM machine for any Windows testing required.
To do create and manage both of these virtual machines I have been using the default Fedora tool virt-manager. For the Linux install I found this to be a breeze. The Windows install was a little less smooth as I needed to pass in the "-no-acpi" parameter during the initial image creation. So to do this one I had to resort to the command line and as the root user issue this command
qemu-kvm -no-acpi -m 384 -cdrom /dev/scd0 -boot d -M pc winxp-pro-kvm.img
Following that when prompted to install any other drivers necessary to boot I had to hold down the "F5" when Windows started. This allowed me to pick from two options. Use a "Standard PC" or "Other". I picked "Standard PC" and the install continued fine. This tip came from the Ubuntu forums.
N ow all I need to do is fire both images up from the virt-manager GUI when needed.
Virt-manager automatically sets up the networking for you, including a DHCP server running on the host virtual networking interface. There was only one more thing I needed to do in order to get the machines fully connected to the Internet just like a normal host. Enable TCP/IP forwarding on the host. That was as simple as adding it to the /etc/sysctl.conf so that everything would be fine for next boot and to get it working straight away, just type this as root.
echo "1" > /proc/sys/net/ipv4/ip_forward
Home and hosed, and now I can do all my work and dev in vitrual machines using completely open source software.
I will let you know how it is all going aftera few weeks.......