Project Virginia? xVM? Whither LDoms?
By Eric S on Oct 24, 2007
Part of the confusion stems from the fact that we recently started using the "xVM" moniker for our x86 based hypervisor technology, since we did not meet the requirements set out by Citrix to continue using the Xen brand. But then, as part of an effort to re-cast all our virtualization technologies under one systems management umbrella (I believe this is what Project Virginia is about), it was decided to expand the scope of technologies included under the xVM brand. The Sun xVM Product Family now encompasses both LDoms & our x86 based hypervisor. Read this blog entry from Marc Hamilton for more details.
Unfortunately, there is still plenty of collateral out there that either implies or explicitly correlates xVM solely with our x86 hypervisor technology. This requires our readers to carefully analyze any information describing xVM, and properly determine from the context whether it's a reference to the overall Sun xVM infrastructure product family, or to one of its members, be it one of the underlying virtualization technologies, or the systems management piece layered on top.
Speaking of systems management, one of the key pieces of the Sun xVM infrastructure is Sun xVM Ops Center, which is under active development by our SysNet organization. Its aim is to provide a systems management framework that truly encompasses all our virtualization technologies. Read more about it in Marc's blog.
So what does this mean for LDoms? Other than the planned support for it in Sun xVM Ops Center, absolutely nothing. Unchanged are the LDoms technology, product, roadmap or name. This includes our plans to support 3rd party management tools via SNMP, our planned extensions to libvirt, or through our own XML-based control interface currently under development. That's a topic for another posting...