The Rise of Virtual Appliances

Virtual appliances deliver focused services in a lightweight package. With all of the talk around virtualization being large system optimization, why single-purpose machines getting so much attention?

The next sound you hear will be the buzz surrounding Virtual Appliances (appliances). However, it isn’t just marketing buzz; this time it’s the real thing. Virtual Appliances are small, specially designed virtual machines that provide a single service or perform a single function. They usually have a significantly smaller operating system footprint than standard virtual machines, a single or very limited number of exposed TCP ports, and a single application. Some appliance examples are mail servers, CMS (Content Management System) servers, web database servers, groupware servers, intrusion detection systems, and dozens more. They provide these focused services in a lightweight and often free package.

So, why all the fuss over small, single-purpose virtual machines? Haven’t we been using these for years? Yes, in fact, we have been using them for years but the difference is that now there are commercial vendors who supply them, support them, and update them as they would any application or proprietary physical appliance. Virtual appliances make the vendor’s job easier in that they no longer have to support several different versions of physical systems in client data centers since virtual machines are hardware and platform independent. Keeping up with BIOS updates, firmware versions, and physical device age (product life cycle), and support issues for hundreds or thousands of client units is painful and costly. Vendor-supplied virtual appliance images available via download are ready-to-deploy and use.

Linux-based appliances have other advantages as well. The operating system is free, most of the applications are free, and it’s easy to maintain locally or remotely. Of its advantages, perhaps the most compelling of all is its customizability including the ability to install a fully functional Linux system within a very small (~500MB) footprint using a system known as JeOS (Just Enough OS)– pronounced “juice.” Most virtual appliance vendors begin with a JeOS system as a base system for a virtual appliance.

Creating a virtual appliance from a standard set of media is time-consuming and requires a high level of system knowledge to remove applications that aren’t necessary for supporting a particular application. To mitigate the need for this high competency level, some vendors (Novell and VMware) provide appliance-building software. Novell’s entry into the virtual appliance-building fray is SUSE Studio: A completely web-based, wizard-driven application (right now in alpha with limited access) that offers several options for a basic appliance (Text only, KDE3, KDE4, Minimal X, and GNOME). Currently, SUSE Studio only creates appliances for VMware or downloadable ISO or USB images but when the product moves to production, you’ll be able to create appliances in Xen, Hyper-V, VMware, OVF, and Amazon EC2 formats. VMware’s VMware Studio is a web-based application built on a virtual appliance. VMware Studio 1.0 is available as a free download from VMware. VMware Studio can be used for individual virtual appliance creation but it’s audience is ISV’s (Independent Software Vendors) or those who build appliances for public or customer consumption.

Virtual Appliance Advantages and Disadvantages


  • Downloadable Virtual Machine Images
  • Free or Low Cost — Support Fees May Apply
  • Ready-To-Use Software and Services
  • Customizable
  • Create Manually or Using Appliance Creation Tools
  • Ease of Deployment
  • Hardware and Platform Independence
  • Small Size


  • I/O Bottlenecks for Write-Intensive Data Backed Applications
  • Most Vendor-Supplied Virtual Appliances are VMware-Centric
  • High Potential for Virtual Machine Sprawl
  • Application and OS Licensing Issues

What about the downside to virtual appliances? Are there issues or concerns that would preclude one from using virtual appliances? As always, there’s a downside to any technology and virtual appliances have few but significant ones. Today, most virtual appliances are VMware only. You rarely find appliances for any other platform. This vendor lock-in may prevent some of you from embracing the idea of virtual appliances until vendor neutral or a more diverse choice for appliances hits the market. Since virtual appliances are small, easy to create, and readily available; their use may lead to virtual machine sprawl which consumes host system resources and storage.

If you’re using licensed applications or a proprietary operating system on your virtual appliances, you may run into licensing issues by deploying unlicensed appliances in your environment. Finally, virtual appliances whose applications are write-intensive, as in the case of some web databases. Disk access and I/O bottlenecks may require rethinking the decision to use virtual appliances for such an application.

Virtualization vendors are all abuzz about virtual appliances and rightly so — they are small, convenient packaged and delivered, function-focused virtual machines that provide enterprise-level service for a fraction of their value.

Don’t know where to start with virtual appliances? Try some of these ready-made ones.

Comments on "The Rise of Virtual Appliances"


Hi Ken,

Great article! For those ISVs who are new to virtual appliances, you should also know that there are physical appliance vendors out there that can take complete responsibility for bringing your application to G.A. as a virtual appliance.

One of them happens to be NEI, (http://www.nei.com/solutiondesign); who has been deploying both physical and virtual appliances for years with JeOS, remote health monitoring, updates and image backup capabilities.

The ROI/metrics behind this is based upon keeping your engineers developing new functionality for your application, rather than diverting their attention to managing the ongoing virtualization process.

- Bill


Thanks for the great article. This is a growing trend, especially for migrating physical appliances to virtual appliances. I would like to point out that in the software world the two different approaches are custom built operating systems (like rPath) or a JeOS (Just Enough Operating Systems or “Juice”, like Unbutu JeOS, Orange JeOS or Novell Suse JeOS) – all of which are Linux-based.

While I agree with wrstetso that the ROI on the software side is in developing & delivering your own applications and not re-building the underlying appliance, with the tsunami of virtualization that we have encountered with our current and new clients, the hardware appliance is becoming the horse & buggy of the ISV industry.

Not to be too biased but VMware does have a raft of free documentation on creating virtual appliances and IBM has announced free classes and an ISV program on porting applications to software appliances.

And lastly, most server consolidation ratios are much larger when software appliances are “consolidated” on to a single server.



Great, thanks for sharing this article post.Really looking forward to read more.


I wish to show my affection for your kindness supporting individuals that must have assistance with this one study. Your personal dedication to passing the message all over appeared to be remarkably useful and have regularly enabled folks much like me to get to their ambitions. Your own insightful guide implies a great deal to me and further more to my peers. Best wishes; from each one of us.


Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>