Year: 2009

Chad Sakac, the Vice President of VMware Technology Alliance at EMC, published today an extensive and informative article about the Virtual Compute Enviroment (VCE) coalition products called Vblocks.

Along with the fresh news about Acadia, this helps a lot to understand the big picture of how the virtualization ecosystem may change in the near future.

First of all, Sakac informs that the coalition is developing a formal certification process to properly recognize as Vblocks a group of core elements that VMware, Cisco and EMC recommend.
This is to avoid that Vblock-like solutions popup everywhere.

Secondarily, and most importantly, Sackac details some of the capabilities of the Ionix Unified Infrastructure Manager (UIM), the management platform that EMC released to control the Vblocks as a whole:

Read more

Along with the announcement of the Virtual Compute Environment (VCE) coalition in November, Cisco and EMC also announced the creation of a joint venture called Acadia, which has the purpose to design the Vblocks products, operate them on behalf of the customers and transfer them from hosting partners to customers data centers if required.
VMware and Intel invested in this joint venture too.

So far there was no additional information about the company but the fact that it will start operating in 2010. Yesterday NetworkWorld provided a lot of details about the board of Acadia:

Read more

In the November 2008 VMware unveiled a plan to bring the hypervisor to mobile phones. 
It announced its Mobile Virtualization Platform (MVP) project and the acquisition of Trango, one of the few startups working in this new market segment.

At the last two VMworld conferences (in Europe and US), the company showed a prototype (a Nokia N800 smartphone) that was able to switch between two different virtual machines, one running a personal environment, and one running the corporate environment. Each one with its own embedded operating system (Microsoft CE 6.0 and Google Android 1.x), each own with independent and isolated user profiles and data.

ComputerWorld is reporting that that prototype was only able to boot one VM at time, and that VMware now plans to run both VMs concurrently, but as far as we saw on stage the parallel execution was already there during the demonstration.
Anyway the article is interesting because it provides insight about the status of the project.

Read more

Any customer interested in client virtualization knows that 2010 will be a critical year for VDI because a number of vendors, including leading players like Citrix and VMware, will begin to release their client hypervisors.

Thanks to the client hypervisors customers will be finally able to adopt server-based computing solutions without losing mobility and flexibility.

Citrix announced that it’s working with Intel on XenClient in January 2009. It was expected to be released before the end of the year, but it seems that it won’t come out before Q1 2010.
VMware too is working with Intel on its Client Virtualization Platform (CVP), which won’t appear before sometime during H1 2010.

Both client hypervisors seem to rely on the Intel vPro technology. And this may be a problem.

At the end of November the Japanese website PC Watch published several Intel documents detailing the company roadmap for its new processors Core i3, i5, i7 and the imminent i9.
One of those documents clarifies which CPUs versions will have vPro and which ones will not:

Read more

In late October virtualization.info described how Fortisphere is slightly changing its go-to-market strategy, revamping its flagship product, now called Virtual Service Manager (VSM).

After just one month the company announces a new VSM feature called vRadar.

vRadar accesses the virtual infrastructure inventory that VSM offers and connects the elements in a logical map.

Read more

A couple of days ago Microsoft published a video series about MED-V that potential customers may want to check out while waiting to understand what the company really plans to do with this product.

The series, which is not available online but can be downloaded here, includes 8 videos:

Read more

There’s much interest around the new major release of Xen because of the rich roadmap that has been proposed and published this summer.

Now we community has a tentative release schedule: January/February 2010.

The news was given by Keir Fraser, Senior Architect at Citrix, during his speech at the Xen Summit in Asia just a few days ago.

Fraser also told that the Xen.org team plans to maintain two branches (3.4.x and 4.x) until the new one is mature enough for the switchover and that a new major release is planned every six-nine months.

Google didn’t release yet its lightweight operating system for netbooks, Chrome OS, and many people already rushed to customize the early source code to create fully-functional images that can boot inside a virtual machine or on real hardware.

One of these early experiments is particularly interesting for the virtualization community because it modifies the Chromium OS open source code to include Xen.

The one that released this project, called ChromiumOS64, is Teo En Ming, who hacked the code to support 64bit platforms (the Google code only supports 32bit architectures at the moment because it targets Intel Atom CPUs that powers most netbooks) and integrate Xen 3.4.3 RC1.

Read more

IBM and VMware recently released a new performance analysis of SAP NetWeaver 7.01 and ERP 6.0 on Windows Server 2008 on vSphere 4.0 on a System x 3850 M2.

The IBM machine, equipped with four 6-way Intel Xeon X7460 CPUs @ 2.66GHz and 128GB RAM, executed up to 12 virtual machines (each with 2 vCPUs), in different scenarios with different virtual hardware configurations.

The benchmark shows that this system supports 8 times more users than a single 2 vCPUs virtual machine.

In late November the FreeBSD team released FreeBSD 8.0.

It finally introduces the experimental support for the Xen domU. This means that FreeBSD 8.0 can run as a (32bit only) Xen guest operating system.

FreeBDS 8.0 also introduce a new experimental feature called “vimage” as part of its OS virtualization technology “jail”, which partitions the network stack.

The vimage jail has its own loopback interface and a separated network stack that includes routing tables. The vimage network interfaces can be moved between different vimage jails and outside of them.