Jason Pearce

In January, my main project at work was to set up three XenServer Enterprise servers and to convert some of our physical machines into virtual machines. This was my first time working with a dedicated virtualization platform that ran at the bare-metal hypervisor level. My prior experience was using VMware’s free VMware Server, which runs as an application running on a Windows or Linux operating system.

Setting up XenServer was rather eventful, which was a good thing. Converting some of our physical servers into virtual machines, however, proved to be more challenging.

What is P2V and V2V

Physical-to-Virtual (P2V) describes the process of migrating a physical server’s operating system, applications, and data from a physical server to a virtual machine guest hosted on a virtualization platform. And virtual-to-virtual (V2V) is very similar, only you are converting a virtual server on one virtual platform — say VMware — to another virtual platform such as XenServer.

One way to move a physical server to a virtual server is to do it the old fashioned way — manually. Basically I’d do a fresh install of a Windows OS in the virtual environment, reinstall of the applications, and them migrate or recreate all of the settings and data the resided on the old physical machine.

Wanting to find an easy way out, I tried my hand at several fully automated P2V software solutions.

Leostream

Leostream’s P2V Direct 3.0 was both my first and favorite solution. They offer one free trial, after that it will cost you about $100 a conversion, which is well worth my time.

Leostream works by installing software on both your XenServer and the Windows OS that you want to convert. Unfortunately, Leosteam only supports 32-bit versions of Windows, but plans on offering a 64-bit version later this year. This was a setback since I had two 64-bit servers I needed to convert.

As for the 32-bit P2V conversions, they went rather well. I did have problems with one server that had two partitions on a single drive, which Leostream support and I couldn’t resolve.

Platespin

Platespin’s PowerConvert was, well, more powerful than what Leostream offered. They also offer a free trial for each XenServer Enterprise license. They have a similar arrangement with virtual provider Virtual Iron.

PowerConvert requires a third-party server. While no software installed on either XenServer or the Windows OS you are attempting to convert, you still have to set up a third server to act as the middle-man during the conversion process. There are many more options offered by PowerConvert, which can be configured via a Wizard or Advance mode. While it was nice having more options, it also added complexity.

Just like Leostream, PowerConvert was incompatible with 64-bit versions of Windows 2003. I still need to find a way to convert two of my 64-bit servers.

VMware Converter

VMware’s Converter is easily the best P2V utility. It is easy to use, it has always worked, it supports both 32-bit and 64-bit versions of Windows, and it’s free. This is the gold standard of P2V software.

Since Leostream and Platespin couldn’t convert my 64-bit Windows 2003 Servers, I decided to attempt a two-step conversion.

• Step 1: Use the free VMware Converter to conduct a P2V conversion
• Step 2: Use the free XenSource Virtual Disk Migration Utility Version 1.1 to conduct a V2V conversion

XenSource Virtual Disk Migration Utility (V2XVA)

The V2XVA Utility is free command-line tool that will convert VMware and Microsoft Virtual Server/Virtual PC virtual machines to the Xen Virtual Appliance (XVA) format. Though this utility lacks a nice GUI and has zero whistles and bells, it’s free and it works. Best of all, I can convert 64-bit operating systems.

The P2V and V2V Procedure:

• Use VMware Converter to perform a P2V conversion
• Open the newly-created virtual machine in VMware Server
• Install remaining drivers and reboot a few times, but do not install VMware Tools
• Once the new virtual machine is stable in VMware Server, shut it down
• Use the V2XVA Utility to covert the VMware virtual machine into a XenServer virtual machine
• Use XenCenter to import the V2XVA-created virtual machine into the XenServer of your choosing

P2VMWC2VMWS2XVDMU2V Conversion

I guess I would call this my physical to VMware Converter to VMware Server to XenSource Virtual Disk Migration Utility to XenServer conversion. Whew. It may make for a long acronym and take a while to run, but it’s free and it works for both 32-bit and 64-bit versions of Windows 2003.

Today Google released an IMAP interface to Gmail. Once you enable IMAP via Settings in your Gmail account, you then need to configure your client to access Gmail via the new IMAP interface.

Since I’ve never been able to figure out how to get the Gmail for mobile application to run on my Windows Pocket PC (because I can’t find a J2ME Java client), adding IMAP now gives me the ability to ditch their Gmail for mobile browser interface and instead use the built-in Messaging client on my phone, which is also known as Outlook Mobile.

And since Google’s Help Center on the “Supported IMAP Client List” didn’t include instructions on how to set up a Windows Mobile Pocket PC, I thought I’d create a brief tutorial. All steps are made within the Messaging client (Start > Messaging).

Step 1: Menu > Tools > New Account

Step 2: Enter your full Gmail email address

Step 3: Wait or skip the Auto Configuration

Step 4: Enter name, username (sans @gmail.com), password

Step 5: Select IMAP4 and name the account

Step 6: Incoming is imap.gmail.com, Outgoing is smtp.gmail.com

Step 7: In Options, set Connection frequency

Step 8: Require SSL and Authentication are necessary

Step 9: Headers Only make things quick

Step 10: Menu > Switch Accounts & Menu > Send/Receive to test

JB and I attended the NiUG conference in Bethesda, Maryland earlier this week. NiUG is a users group for iMIS, the CMS and CRM tool Lambda Chi Alpha recently adopted.

Conference Photo Pool

more photos from conference

The conference was great. JB had the chance to meet other iMIS developers and learn some of their tricks, while I learned about Crystal Reports and upcoming .NET solutions. Being my second NiUG conference, there were many familiar faces.

Today, our staff began using the Live version of iMIS, Lambda Chi Alpha’s new CRM.

Aside from a few bugs and missed procedures, our staff and iMIS got along just fine. Three of our team members spent most of the day processing membership status changes while JB and I tackled the biggest bugs.

I just want to publicly thank the team members involved with this project:

• Joe Klimek, CFO, deal closer, and backup techie / project manager
• JB (Joshua Bennett), SQL guru and lead developer
• Doug Morris from CSI, our reseller, vendor, and support
• LCA Staff, for being patient and supportive as we switch from a 10-year-old CRM to a new way of managing our members and information

Thank you all. We still have a lot more to accomplish, but the beginning is finally here.