Of Wine, Virtualization and xVM

A few years back, I remember sitting with a group of customers talking about wine, and virtualization (a natural pairing, if ever one existed). Wine, because we were at an event Sun was hosting in Napa Valley, the heart of California's wine country - virtualization, because the attendees were data center professionals who'd come to talk about the future. The customers in attendance all ran very high scale, high value data centers, who would deservedly respond to the accusation that they "hugged" their servers with "and what of it?" They were the individuals who kept some of the world's most valuable systems running with exceptional reliability. But they were all starting to see and worry about the same thing, running applications in "virtualized" grids of networked infrastructure ("cloud computing" wasn't yet in vogue, or I'm sure someone would've used the term). Now, virtualization is a simple concept with a fancy name (abbreviated to "v12n" by the cognoscenti - by that method, I am "j14z"). It's simply slicing up physical computers into many smaller "virtual" computers, each of which can be outfitted with its own OS and application stack. That is, not only does a virtualized computer take on the task of running multiple OS's (running atop a hypervisor, described below), but the OS's themselves might change over time, responding to load or schedule. The traditional view of "computer A runs OS/Appl...

Date: September, 15 2008
Url: http://blogs.sun.com/jonathan/entry/xvm1

Others News