KVM & Virtual Machine Manager in Foresight

Foresight has long been a proponent of KVM over other virtualization technologies such as Xen or Virtualbox.

If you, like me, aren’t a guru on the command line and prefer using a GUI, Virtual Machine Manager is available in the Foresight repositories. If you’ve used Virtualbox or VMWare, you’ll find virtual-manager very familiar. The only downside (for some), is that you will need a modern processor that supports Intel VT or AMD-V.

Let’s get started:

In this example, we will use an ISO of a Linux distribution. Go ahead and download an ISO of a Linux distro you’d like to try out.

From a command line install the tools you’ll need:

sudo conary update virt-manager libvirt

You’ll want to install it from the command line, as PackageKit has a bug that it doesn’t pull in libvirt:runtime for some reason. (FL-2050)

Start the service:

sudo service libvirtd start

Go to Applications -> System Tools and choose Virtual Machine Manager.

PolicyKit will prompt you for your password. Enter it and Virtual Manager will start.

Click on localhost.

Then click File -> Add Connection and click Connect.

Click New in the bottom right hand corner. You will be prompted to enter the name of your new Virtual Machine.

You will now be present with 5 steps to create your Virtual Machine:

Step 1: Enter the name of VM you wan to create

Step 2: Click on “Use ISO Image” and then “Browse” and chose the ISO you downloaded earlier. Then from the drop down boxes choose Linux, and in the second drop down box you can check if the distro you’re trying is available.

Step 3: Choose how much RAM and how many CPUs the VM can use

Step 4: The defaults should work – choose to enable storage, and how much hard drive space the VM can use. (I’ve learned that hard drive space is important – these VMs need more than you think they will!)

Step 5: The defaults should work here as well, but you can click on Advanced Options if you want to change the Networking options. I’ve never had to change anything here, and Networking has worked out of the box.

And that’s it! Now under “localhost” double click the name of the VM you created, and it will boot up, just like a computer was booting up. You’ll install the Linux distro, just like you would on to a hard drive. One thing I’ve noticed, is that after an installation, it needs to reboot. My experience is the VM shuts down, rather than rebooting, but just starting it up again, the VM will boot up th eOS after your install.

To use the mouse, just click your mouse inside the virtual machine. To regain control of your mouse, press control and alt and your mouse will work normally inside Foresight again.

Here is a screenshot of Virtual Machine Manager running while the GNOME Dev Kit loads (note I have created VMs for the Dev Kit and the betas of Fedora 11 and Ubuntu 9.04:

GNOME Dev Kit

This screenshot shows the GNOME Dev Kit and Fedora 11 running side by side (One interesting thing about running Fedora is that i don’t have to release the mouse via ctrl-alt, it’s automatic within the OS. I’m not sure why, maybe it’s because Virtual Machine Manager is developed by Red Hat?):

Virtual Machines

If you have a modern processor, the hard drive space, and some memory to spare, I highly recommend Virtual Machine Manager. It makes creating and running different operating systems a breeze.

Related

comments powered by Disqus