In your own private cloud, there are a number of ways to work with virtual machines. Amazon's cloud uses Xen for its virtualization infrastructure, but in your own cloud, you are free to use Xen or KVM or Virtualbox, or whatever else you want. Lacking an EC2 console, administering and working with VMs in your cloud will require you to choose your own admin tools. There's always the command line, of course; you can launch a KVM or Xen machine without a GUI, but there's also a nice graphical program called virt-manager that I'm rather fond of; literally the 'Virtual Machine Manager' (see Figure 1). Using this tool, you get a bird's eye view of running virtual machines, including live performance graphs for network, CPU, and disk usage. The Virtual Machine Manager also makes it easy to communicate with other hosts running virtual machines; that would be your private cloud. It gets better; virt-manager works with both KVM and Xen, two common virtualization frameworks.
Figure 1 : Once connected Virt-Manager shows you all configured machines whether they are running or not.
The virt-manager application displays information about each machine, its run state, number of processors (VCPUs), memory usage, and CPU usage. It also lets you adjust the resources for a given virtual machine, adding processors, memory, or even extra storage. There are tools for cloning VMs, creating new VMs, and communicating with VMs using a full graphical console; point and click. The latter is done using a built-in VNC client.
Most distributions have virt-manager in their repositories, but they sometimes tend to run well behind the version available directly from the Website itself (long term support distributions are particularly problematic that way). I don't find myself suggesting this often in 2011, but I highly recommend that you get the source and compile the latest version yourself. It's all Python code so perhaps compile isn't quite the right word but while you're there, make sure you also download the latest 'virtinst' code and prep that as well; virt-manager relies on it.
When you run virt-manager for the first time (see Figure 2, from a different machine), you'll find yourself looking at a rather sparse window, especially if you have no VMs currently running on the host system.
Figure 2 : The virt-manager application at start. No connection and no virtual machines.
When Virt-Manager starts, it will look to the host system, the 'real' hardware on which the virtual machines are running. Depending on the setup, the machine may be disconnected, at which point you will right click on the 'localhost' machine, and select Connect. Once this is done, you should then see all the virtual machines running on the system as shown in Figure 1).