Vagrant is an amazing tool for managing virtual machines via a simple to use command line interface. With a simple vagrant up you can be working in a clean environment based on a standard template.
Red Hat is emphasizing KVM’s scale-up capabilities with today’s beta release of Red Hat Enterprise Virtualization 3.0.
The updated KVM hypervisor supported with Red Hat Enterprise Virtualization (RHEV) 3.0 is based on Red Hat Enterprise Linux (RHEL) 6.2. Among its capabilities is support for up to 2 TB of memory and up to 64 virtual CPUs per virtual machine (VM). By contrast, VMware’s forthcoming vSphere 5 will support up to 1 TB of memory and 32 CPUs per VM.
XEN allows several guest operating systems to execute on the same computer hardware and it is also included with RHEL 5.5. But, why use KVM over XEN? KVM is part of the official Linux kernel and fully supported by both Novell and Redhat. Xen boots from GRUB and loads a modified host operating system such as RHEL into the dom0 (host domain). KVM do not have concept of dom0 and domU. It uses /dev/kvm interface to setup the guest operating systems and provides required drivers.
Back to QEMU network 101, there are several ways to configure QEMU network, the default which happens to be the easiest is "-net user" this is a very neat function implemented by QEMU - it creates a virtual router (with virtual DHCP server, virtual DNS, etc) it uses 10.0.2.x address.
Now, here comes the confusing part. QEMU supports tap device ("-net tap" instead of "-net user"). And its official document says "... you can then configure it as if it was a real ethernet card." But how? if everyone is as familiar with TAP device as the QEMU author, probably I won't need to write this (at least it would have saved me 4 hours if someone has written something like this :-)
QEMU supports networking by emulating some popular network cards (NICs), and establishing virtual LANs (VLAN). There are then three ways to internetwork QEMU guests.
Various posts relating to VMware within HPC/Cloud type environments.
Hyper-V Server is the free to download hypervisor from Microsoft. Licensing-wise, it has a teeny tiny niche market.
KVM (Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions Intel VT or AMD-V.
Design guidance and best practices in deploying Cisco Nexus 1000V Series Switches-software switches embedded within the VMware vSphere hypervisor-on top of the Cisco Unified Computing System™, focusing on deployment options using the various adapter types that the Cisco Unified Computing System supports.
Proxmox Virtual Environment is a powerful Open Source Server Virtualization Platform, based on KVM and OpenVZ.
"Docker is an open-source project to easily create lightweight, portable, self-sufficient containers from any application. The same container that a developer builds and tests on a laptop can run at scale, in production, on VMs, bare metal, OpenStack clusters, public clouds and more. "