Hypervisors & Experiments

Hypervisor1- VirtualBox running on Windows 7 64bit - (Sata disk 1)

Hypervisor2 - Workstation running on Windows7 64bit - (Sata disk 1)

Hypervisor3 - Hyper-V within Win2008 R2 - (Sata disk 1)

Hypervisor4 - XENServer - (Sata disk 2)

Hypervisor5- ESXi - (Sata disk 3)

Experiment 1 - Crashme - sending non-sensical data to a VM (WinXP least secure) with the intent of causing a full crash of the VM itself, if not a full crash the vCPU will have to deal with non-sensical instructions

Experiment 2 - Fuzz Testing - sending random messages via specific programs causing CPU & Mem overloading of a VM, this can cause some application to crash, however my intent is not to test FUZZ, however see it's effect on other VM's within the same Host.

Experiment 3 - Fork Bombs... - By initializing a fork bomb - (causing a process to create unlimited child processes ) can over load the memory within a VM, causing it to become unstable or actually hang/crash - Divided into 3 sub experiments in which 3 out of 4 running VM's are hit with Forkbombs

Experiment 4 - DoS attack - Attack using 2 zombie machines (not located on the host) to attack using a TCP syn storm a target VM within the hosted environment, This server should become unstable, let alone the flooding of the v network cards / physical network card.

Hypervisors dropped:

Parallels running on Windows 7 64bit (Type 2 Hypervisor)

Reason: Unable to run experiment 4 on target VM

Issue: Parallels only uses NAT for virtual networking from Virtual Machines via host NIC through to the physical network, therefore the VM's IP address is a private IP inside the Host on the Virtual Switch.

In order for Experiment 4 to work Bridged networking must be in place, which using dynamic IP's via a DHCP service or Static IP's each VM has it's own MAC & IP address visible through the physical NIC on the physical network.

KVM runnning on ubuntu 10.4

Reason: Same as above, unable to configure virtual switch for bridging & also unable to grab/ungrab VM's desktop for MS machines using the AQEMU management console within KVM.

As a result via both problems I was unable to test and even configure all test VM's on this platform due to AQEMU freezing up.