ATLANTA — Thoughts collected while going up and down seven or eight escalators to get from one TechEd session to another…
VMM 2012: The beginning of the end for Virtual Server?
According to various reports around the blog- and Twittersphere from Microsoft users and partners, System Center Virtual Machine Manager (SCVMM) 2012 will not support Microsoft’s Virtual Server 2005 R2 as a virtual machine host. This has users wondering if the release of SCVMM 2012 will represent the beginning of the end for Microsoft’s original hypervisor technology.
More items from the Hyper-V wish list
Users at TechEd explored Dynamic Memory and storage integration for Hyper-V, but there were also some miscellaneous items on their wish lists:
- “Bare metal provisioning will be nice to see in VMM 2012,” said Nathan Lasnoski, a Microsoft MVP who does field deployments of Hyper-V for clients as a systems integrator. “Right now we’ve developed an efficient pattern for doing deployments, but it will be much easier just to spin up a Hyper-V host through software.”
By Beth Pariseau, Senior News Writer
ATLANTA — NetApp and Cisco have issued another reference architecture in partnership with a virtualization vendor. This time it’s Microsoft.
The NetApp Hyper-V Cloud Fast Track with Cisco data center architecture, announced Monday at TechEd North America, is a pre-tested reference architecture that includes Hyper-V, System Center, NetApp storage and Cisco’s Unified Computing System. A software bundle that includes the NetApp OnCommand”3.0 plug-in for Microsoft is also included.
To create that OnCommand plug-in, NetApp is using an Opalis-based workflow management system layered over several hundred custom PowerShell commandlets to communicate with System Center, rather than the Storage Management Initiative — Standard (SMI-S). Microsoft officials had said previously that SMI-S would be the basis for integration between storage partners and System Center Virtual Machine Manager (SCVMM) 2012.
VMware’s acquisition spree continues today with Shavlik Technologies.
Shavlik is VMware’s partner in VMware Go, a service designed to help SMBs deploy and manage virtualization more quickly and easily. The 18-year-old company built its business around security, with a focus on patch management. (Shavlik’s technology helps power VMware Update Manager, for example.)
The Shavlik acquisition makes sense given VMware’s new focus on the applications market. After all, it wouldn’t do VMware much good to buy Zimbra and SlideRocket without having some way to easily update and patch those applications. And Shavlik was the natural choice, thanks to its existing partnerships with VMware on Go, Update Manager and other initiatives.
But it sounds like Shavlik will also play a role in VMware’s increasingly complicated infrastructure management strategy.
A new product announced by VMware parent company EMC Corp. this week could lay the groundwork for live migration of virtual servers over large geographic distances. But storage is just one part of that battle and some experts question whether the cost of long-distance vMotion will be justifiable even when the technology is ready for prime time.
At last week’s Red Hat Summit, company execs painted Microsoft as their bitter rival. But the two vendors may have more in common than you’d think.
I was reading Beth Pariseau’s story on KVM’s slow go of it in the virtualization market, and I started to sense a pattern: A lot of the reasons that Red Hat Summit attendees gave for not moving to KVM were the same reasons that other IT pros have given for not deploying Microsoft Hyper-V.
To illustrate this point, here are some snippets from that story, with one change: I replaced “KVM” or “open source software” with “Hyper-V.” Check it out:
Red Hat Enterprise Linux (RHEL) 6 and Red Hat Enterprise Virtualization (RHEV) 2.2 offer some options for memory overcommit, but these features can interfere with one another in some scenarios, according to IBM engineers.
Red Hat and IBM formally announced a partnership to develop RHEL KVM and RHEV together at last week’s Red Hat Summit in Boston. Also at the show, Joel Schopp, a Linux software engineer for IBM, presented an open-source utility, Memory Overcommit Manager (MOM), meant to reduce the interference between the memory overcommit features in RHEL and RHEV.
BOSTON — By nature, virtual machines (VMs) are movers and shakers. The tools in Red Hat Enterprise Linux (RHEL) 6 perform the essential tasks of virtual-to-virtual (V2V) conversions, physical-to-virtual (P2V) conversions and live migrations, but they still have room for improvement.
Matthew Booth, a Red Hat senior software engineer, revealed a few expected improvements at the Red Hat Summit this week. RHEL’s P2V conversion tool, virt-p2v, is still fairly new, so the company is working on faster conversion times and improved fixed-storage transfer options, Booth said.
If your organization is just starting to virtualize, P2V conversion is a critical first step. Slow conversions can complicate virtualization implementations, so RHEL 6 needs to step up its game in this area.
BOSTON — Red Hat Enterprise Virtualization (RHEV) has about 500 customers worldwide, and more than half are existing VMware users.
“We also have customers who have a lot of VMware,” he said. “That’s actually the majority of our customers right now.”
These VMware users are looking for more affordable alternatives to virtualize more of their infrastructure, he said.
“One of the major issues comes down to cost,” he added. “VMware is a fairly expensive product, and there are lots of applications in my environment that I’d like to virtualize that I can’t at $3,000 a socket.”
About two-thirds of RHEV users are existing Red Hat customers (either Red Hat Enterprise Linux or JBoss), Dubuque said. And in addition to the 500 customers, there are another “couple hundred” active proof-of-concept deployments, he said.
Dubuque also previewed RHEV 3, which will come out by the end of the year.
BOSTON — New details have emerged regarding Red Hat Enterprise Virtualization (RHEV) 3.
Chuck Dubuque, a Red Hat product marketing manager, shared the details during a RHEV overview session here at the Red Hat Summit. He said a RHEV 3 beta will come out later this summer, and the final version will be out by the end of 2011.
RHEV 3 will support the following density numbers:
- 4,096 cores per CPU
- 64 TB of RAM per host
- Up to 32 vCPUs per guest (with support for 64 vCPUs in the works)
- 1 TB RAM per guest
- 200 hosts per cluster
In addition, RHEV 3 will no longer require Windows to run its management component. The release will not include storage live migration, but Dubuque said “we’re working on that now” and it should be available in Red Hat Enterprise Linux 6.2 or 6.3, due sometime next year.