Review: Virtual Iron 3.5 offers a flexible, low-cost fix with impressive provisioning capabilities.
Virtual Iron Softwares Virtual Iron builds on the Xen hypervisor and other open-source components to form an effective virtualization solution with a price tag low enough to keep market leader VMware on its toes.
During tests of Virtual Iron 3.5, eWEEK Labs was particularly impressed with the products provisioning capabilities: We simply plugged our virtualization host servers into a management network, and PXE (Preboot Execution Environment) booted them from Virtual Irons management server. Once the servers were up, we could begin creating and assigning virtual machines to our nodes right away.
One of the biggest differences between Virtual Iron 3.5 and early Xen-based virtualization products is Virtual Iron 3.5s ability to virtualize pretty much any x86- or x86-64-based operating systemwithout a special, Xen-aware kernel.
Virtual Iron and other current Xen-based virtualization products manage this modification-free virtualization by running on top of Advanced Micro Devices and Intel processors that feature AMD-V and Intel VT hardware extensions, respectively.
Most notably, this hardware support brings Windows within Xens ken, a capability that VMwares products have long enjoyed. However, unlike XenSources XenEnterprise, Virtual Iron 3.5 offers no option for running on hardware without virtualization extensions, which could be a problem if youre hoping to tap virtualization to squeeze more out of your existing machines.
However, the hardware extensions on which Virtual Iron relies are becoming de rigueur for most machines. Whats more, after taking into account Virtual Irons cost advantages over VMwares products, enterprises that choose to go with Virtual Iron might find that they can afford to make some hardware purchases with their savings.
The full-featured enterprise edition of Virtual Iron 3.5which includes live migration, failover and capacity management functionality, as well as support for Fibre Channel SAN (storage area network) and iSCSI storagecosts $499 per socket. VMwares VI3 Starter is priced similarlyat $1,000 per pair of CPU socketsbut it lacks support for SAN or iSCSI storage. VMwares VI3 Standard sells for $3,750 per pair of CPU sockets; VI3 Enterprise, which adds support for VMotion live migration and other high-availability features, costs $5,750 per pair of CPU sockets.
We tested Virtual Iron 3.5 Enterprise Edition using the free, 30-day trial license
. Also available is a free, single-server version of Virtual Iron, in which the management server and virtualization host live on the same machine.
Virtual Irons management server runs on Linux and Microsoft Windowsspecifically, on Red Hats RHEL (Red Hat Enterprise Linux) 4 U2 (Update 2) and U4 (Update 4) 32- and 64-bit; Novells SLES (SUSE Linux Enterprise Server) 9 SP (Service Pack) 3 32- and 64-bit; Windows XP Professional 32-bit; and Windows Server 2003 32-bit.
eWEEK Labs tested the Virtual Iron management server, which is Java-based, on Windows Server 2003 SP2 and on CentOS 4.2 (a clone of RHEL 4 U2).
Click here to read about VMwares latest virtualization offering.
Also cross-platform-friendly is Virtual Irons Management Console, a fairly rich application that depends on Sun Microsystems Java Web Start application technology.
Using the console, we were able manage our nodes equally well from Windows and from Linuxsomething we found particularly refreshing after coming off our testing of VMwares Virtual Infrastructure product, which is disappointingly Windows-bound on both its management server and client application sides.
Virtual Iron can host pretty much any x86 or x86-64 operating system, but theres a significant set of functionality that requires add-on software, called VS Tools, that Virtual Iron makes available only for a handful of operating systems (the same Windows and Linux versions that are on Virtual Irons list of supported management servers).
VS Tools are required for Virtual Irons LiveMigrate and LiveRecovery features, to view performance information on guest instances from the management console, and to shut down or reboot guest machines gracefully (as in not simply pulling their virtual plugs) from the management console.
For Windows guests, these tools take the form of an .exe installer with Virtual Iron-enhanced device drivers. For Linux, Virtual Iron provides binary packages containing drivers compiled to match supported kernels.
Wed like to see Virtual Iron adopt a less rigid approach to delivering these tools for Linux. VMware, for example, allows administrators to compile the drivers to match the kernel theyre running, rather than limit support to a handful of options.
This sort of flexibility would have helped prevent one of the snags we encountered during testing: We installed the x86-64 version of CentOS 4.4, and, probably because the VM wed created sported a single processor, the CentOS 4.4 installer installed the uniprocessor version of the Linux kernel. Virtual Irons VS Tools packages come in SMP (symmetric multiprocessing) flavors only, and an SMP kernel must be installed to install the tools properly.
When we installed the SMP kernel for our system from its network repository, however, the version we pulled down was different from the version that the VS Tools package was expecting, so we had to revert to the older kernel for the tools to work.
We were surprised to find that Virtual Iron does not offer its VS Tools for rPath Linux because Virtual Iron and rPath have a partnership in which rPath has added Virtual Iron as a build option for software appliances created with the rBuilder platform.
The management console.