moxiefoxtrot

…a random blog about life and technology

Archive for the ‘Virtualization’ tag

Installing Ubuntu 8.10 in VirtualBox

18 comments

I mentioned a couple days ago in a quick write up on installing Ubuntu 8.10 in VMware Fusion that I would take a look at the process of installing Ubuntu 8.10 in VirtualBox. VirtualBox, unlike other desktop virtualization products is free for personal use and is opensource. It allows users to install a wide variety of operating systems without having the overhead of physical hardware.

Installing VirtualBox is pretty easy, download the application which supports Windows XP, Linux 32bit/64bit, OS X, Solaris and OpenSolaris as the host operating system and then follow the on screen instructions to complete the installation.

In this article I’ve used the OS X version of VirtualBox because my Mac was handy at the time. However, the screenshots are similar regardless of the operating system you have VirtualBox installed on.

The goal of this article is to show novice users a step by step installation of installing an Ubuntu Desktop inside of VirtualBox without having to mutli-boot their computer. I am going to assume you have VirtualBox installed and have either downloaded the Ubuntu ISO image or have an Ubuntu CDROM handy.

Creating the Ubuntu virtual machine

  • Open VirtualBox and create a new virtual machine and click the “New” Icon. A new wizard window will appear as shown in (Figure 1), click “next”.
  • Enter the name of your new virtual machine perhaps “Ubuntu810Desktop” and then select “Linux” from the drop down Operating System menu, Ubuntu 32bit will highlight by default, click “Next” (Figure 2)
  • Select the amount of RAM you wish to dedicated to your Ubuntu Desktop, the default is 256MB however, 512MB would give you better performance if you have the available RAM, click “Next“. (Figure 3)
  • Next, you will be presented with the option to create a new virtual Disk. Click the “New” button and another window will appear (Figure 4), click “Next“, you are presented with an option to for “Dynamic” or “Fixed” storage. Dynamic storage will grow the virtual disk as you require more space (saving space on the hard drive) whereas Fixed storage will pre-allocate the space. I’ve selected “Dyanmic” for this installation (Figure 5), click “Next“.
  • Enter the name of the virtual machine and select the amount of space you wish to give your Ubuntu Dekstop, I’ve opted to use the default of 8GB. (Figure 6, Figure 7) Click, “Next” and finally “Finish” to complete the creation of the virtual disk for the Ubuntu Desktop.
  • You will be dropped back to the virtual disk screen and  you will notice the new virtual disk, click “Next” to continue. (Figure 8 )
  • Finally, the last screen will give you a general overview of the virtual machine, click “Finish” to complete. (Figure 9 )

Installing Ubuntu

  • Now that the virtual machine template has been created we can begin the installation of Ubuntu. The first thing we need to do is attach the Ubuntu ISO image or CDROM to our virtual machine. Click the CD/DVD-ROM link, its blue (Figure 10 ) a new window will appear as shown in (Figure 11).
  • Check the “Mount CD/DVD” button and then select either “Host CD/DVD” if you have the CDROM or “ISO Image file” if you have the ISO image. I’ve used the ISO image in this example, click “Ok” to complete. (Figure 11, Figure 12)
  • Select the virtual machine from the left menu in VirtualBox and click the green start arrow to turn on your virtual machine. You will be presented with a new window and a warning (Figure 13) click “Ok” to dismiss this.
  • NOTE: Once you click in the virtual machine window your keyboard and mouse are locked in.
  • Your virtual machine will now restart and the Ubuntu installation will begin (Figure 14), select the appropriate language and press “enter“. You will be presented with another window telling you how to exit the screen (Figure 14a), click “Ok
  • Next, you will be presented with a menu (Figure 15) using the arrow keys select the “Install Ubuntu” option and press “enter“. Installation will begin as shown in (Figures 16). Once the installer has loaded a new window will be presented starting the actual installation (Figure 17 ) the language you selected in the previous screen should already be highlighted. Click “Forward“.  
  • On the next screen select your timezone and click “Forward” (Figure 18), select your keyboard language layout (Figure 19), click “Forward“.
  • Next, you are presented with the disk partitioner. We are going to use the defaults here which is “Guided – use entire disk“, click “Forward” to continue the installation.(Figure 20)
  • Next, you will be presented with a series of questions pertaining to setup of your user account. Fill in the fields with the acceptable information and click “Forward“. (Figure 21)
  • At this point installation is ready to begin, look over the proposed settings and click “Install” when you are ready. This will take a few minutes to complete. (Figure 22)
  • Figure 23 is an example of what you can expect along the way during installation.
  • When the installation is completed you will be prompted with a windows requiring you to restart the computer. (Figure 24) Things got kind of weird at this point, since the CDROM is attached to the virtual machine un-mounting it by going to the “Devices > Unmount CD/DVD-ROM” would do no good since the virtual machine would reboot off the CDROM again. I couldn’t find a decent way to remove the CDROM from the virtual machine unless I powered it off. So, hit enter to restart the virtual machine and then power it off by click the “X” on the window. You will be presented with three options select “Power off the machine” and click “Ok“.
  • Select the virtual machine and click the green “start” button again.
  • Once your machine has rebooted you will be prompted with a login screen as shown in (Figure 26) enter the username and password you specified during installation to log into Ubuntu. You will now see your desktop (Figure 27).

Installing the guest additions

  • Now, that our Ubuntu operating system is installed we need to install the “Guest Additions” these are similar to the VMware Tools that VMware provides.
  • From the VirtualBox menu select “Devices > Install Guest Additions” a CDROM will appear on your desktop and give you a warning just click “Cancel” it’s trying to auto-run as if it was in Windows. Navigate to “Applications > Accessories > Terminal“.  
  • Enter the following command to switch to the CDROM directory “cd /cdrom“. Invoke the installer by running the following command “sudo ./VBoxLinuxAdditions-x86.run” if you have a 32bit platform or “sudo ./VBoxLinuxAdditions-amd64.run” if you have a 64bit platform. (Figure 28)
  • Once the Guest Additions are installed, reboot and you will be presented with a window telling you the benefits of them. Click “Ok” to dismiss the window. (Figure 29)

Enjoy Ubuntu. :)

Edit: Andreas pointed out in a comment below of an issue with keyboard layouts using Ubuntu 8.10 and Windows XP SP3. You can find more information here.

Written by Ryan

January 5th, 2009 at 1:12 pm

USB devices with VMWare ESX

one comment

I decided to do a short write up on using USB devices on your virtual machines inside of VMWare ESX. One of the challenges the company I worked faced when moving our physical servers to virtual machines was the fact some of the servers required a USB dongle for the software to run.

Unlike other VMWare desktop products such as Workstation or Fusion, ESX doesn’t allow you to utilize the ESX servers native USB ports and map them to a virtual machine.

We first tried a solution from Digi called AnywhereUSB, the product works well and is very stable and cost about $250 per unit. However, the down fall was we wanted to utilize the extra ports for other servers. At the time (and this still me be the case) the AnywhereUSB product wouldn’t allow multiple virtual machines to connect to the device and share the ports, we needed a solution that would allow separate virtual machines to connect to a dedicated port.

The second and final solution was a product from Lantronix called UBox, specifically the 4100 model and it cost around $150. It allows for 4 USB devices to be connected and each port can be specifically dedicated for a virtual machine, allowing us to connect 4 USB devices to 4 separate virtual machines without them knowing about each others devices. You can also have the operating system auto connect back to the USB device when the server is rebooted to ensure the hardware is always there by using the configuration software.

The simple configuration application will sit in the system tray of Windows. Below are a few screen-shots of the application (sorry for the nasty edits).

You’ll  notice the second image is giving us a warning about the software version we are running, it’s because it’s running on Windows 2000.

One of the cool things about these Lantronix units is that we are able to connect Windows 2000 and Windows 2003 virtual machines to the same UBox. The device comes with the Windows XP, 2003 software however the Windows 2000 software can be downloaded on the companies website.

In the end the Lantronix unit performs well, we have it setup on a private network and have had relatively few problems.

Written by Ryan

December 22nd, 2008 at 2:18 pm

EqualLogic PS5000x w/ Vmware ESX 3.5 – Part 1

3 comments

I had the opportunity to spend some time working with a Dell EqualLogic PS5000x SAN yesterday and here are some of my initial thoughts.

3 x Dell 1950, 2.4ghz Dual Core, 16GB ram
Vmware ESX 3.5U1
1 x Intel 100/1000 Ethernet port (iscsi)
1 x 3com 4924
1 x EL PS5000x  16×400GB SAS, 10K Drives
Using software ISCSI initiator

Pro’s
Snapshots are very efficient and effective. I loaded up a few 10GB virtual machines on a LUN, took a snapshot and delete them. You can’t restore while the LUN is online so you need to take it offline to restore, however you can take the snapshot and make it read/write and mount it while the main LUN/Volume is online.

After restoring from the snapshot all the data was in tact.

You can delete snapshots after so many days, schedule automatic snapshots etc.

The management interface is very, very user friendly and intuitive. It works best if you run it outside the browser. If you run it in the browser IE performs the best.

Thin provisioning is pretty interesting and will definitely prove viable in certain scenario’s.

You are able to setup LUNS/Volumes to be automatic, raid5, raid50 or raid10. This is independent from the storage pool configuration. For example if you have multiple storage pools across multiple members with different raid specifications it will automatically move your data and find the best fit on the raid type you specify. If you leave it set to automatic it will do an analysis and migrate data to the area’s were it will get the best performance. When I get access to a second unit I’ll be testing this out.

Volume/LUN cloning is pretty simple and straight forward, you can clone the Volume/LUN while its online however you cannot setup thin provisioning on the clone if the original LUN/Volume doesn’t have thin provisioning enabled.

Con’s
There is no dedicated management Ethernet interface. It’s a shared “group” IP address that floats between all three active nic’s on the controller.

According to Dell the next firmware which will be 4.0 and it will have the ability to specific a specific Ethernet port from the controller and make it a dedicated management port. But we will loose a ISCSI port that way so it might not be a viable option. The controllers can also be managed via serial cable.

Applying new firmware takes about 60 seconds and during this time both controllers are unable to serve data. An engineer told me that the next firmware will decrease this to about 20-30 seconds.

Misc thoughts
There is about a 10% slow down in read/write speeds when using straight vmdk files compared to storing the main vmdk file on local or fiber and then using the MS ISCSI initiator to mount the ISCSI lun. The downfall to using the MS ISCSI initiator is the amount of CPU it uses, almost 80% more then using straight vmdk disk.

Reads and writes are generally about 20-25% slower on the ISCSI then on the fiber disk. However, I think the demo setup is sort of gimped as we are only using 1 connection to the ISCSI network from the esx server and the switch we are using isn’t exactly the best choice. It seems to cap at about 40-50MB/s.

The I/O response times were about 10ms more on ISCSI then on the fiber disk. For example 13.4ms on fiber and 24ms on ISCSI.

More tests will be needed. However, while its generally a little slower given the nature of it the performance is still fast and efficient and with HBA’s and better switches I have no doubt these numbers will change.

Using IOMeter for my tests inside a virtual machine the servers cpu usage was about 2-5% lower on the ISCSI virtual machine as compared to the Fiber virtual machine.

There is much more to test and explore but these are my initial thoughts and I figured I would share them.

Written by Ryan

July 25th, 2008 at 11:50 am

Posted in Virtualization

Tagged with , , , ,