KVM Virtualization With Enomalism 2 On A Fedora 10 Server - Page 2

3 Using Enomalism

You should now be at the Enomalism login prompt. The default username is admin, and the password is password (you should change this after the first login):

This is how the Enomalism control panel looks. The Dashboard lists all transactions and tells you if they were successful or not:

To run KVM guests, we can either create our own virtual machines or download preconfigured virtual machines from the public Enomalism repository. I will describe both methods in this tutorial. Right now I'm going to show how to use a preconfigured virtual machine from the public Enomalism repository.

There are one or two things to note about the preconfigured appliances. First, they have a disk space of only 1 GB, so they are probably not for production use, and second, it is possible that they won't be able to bring up their eth0 interface, i.e., they will have no networking (this happened to me when I downloaded the Ubuntu 8.04 KVM appliance; however, when I downloaded the CentOS 5.2 KVM appliance, networking was working fine).

3.1 Using Preconfigure Appliances

Go to Repository > REMOTE APPLIANCES. Find the virtual machine that you'd like to use and click on the plus sign in front of it (I'm going to download the CentOS 5.2 KVM guest - make sure you select a KVM guest and not a Xen guest!):

Confirm your selection:

The appliance is now being downloaded in the background. This can take a few minutes. You can see the download status on the Dashboard (click on the blue refresh icon to update the status):

This is how it looks after the download has finished:

You should now find the appliance under Repository > LOCAL APPLIANCES:

Before we start the appliance, we have to provision it (this means, the appliance is just a template from which we create KVM guests). Go to Virtual Infrastructure > ELASTIC VALET and select the CentOS 5.2 KVM appliance. In the other drop-down menus, select default, then scroll down:

Right now, we want to create just one guest, so we select 1 in the Number of machines to provision drop-down menu. Click on Provision afterwards:

The template is now being unzipped. Again, this can take some minutes, and you can check the status on the Dashboard:

Afterwards, go to Virtual Infrastructure > INFRASTRUCTURE. Click on the refresh button in the left frame. You should find that server1.example.com is a member of the cluster named default, and that there's one virtual machine on server1.example.com (named 814f4b... in this example). Click on that virtual machine in the left frame, and the virtual machine summary should load in the main frame:

It's a good idea to rename the virtual machine to something less cryptic, so click on the pencil left of the virtual machine name...

... and give the virtual machine a new name:

You can now start that virtual machine by clicking on the start this virtual machine link:

Confirm that you want to start the virtual machine:

In the virtual machine summary, there should now be some new links (e.g. suspend, poweroff, reboot). The interesting link is the one that reads VNC to this VM (via the parent). This will open Enomalism's built-in VNC client (written in JAVA). (Of course, you can use any other VNC client to connect to the virtual machine, e.g. TightVNC. In the lower right corner of the summary, you will find details how to do this (IP and port).)

This is how the JAVA VNC client looks (the default login for the public Enomalism appliances is root:password):