Paper: Enhanced VMware ESX 4.1 CPU Scheduler

In the last few days virtualization.info recommended a couple of new/refreshed, very interesting papers from VMware: The Design and Evaluation of a Practical System for Fault-Tolerant Virtual Machines and Understanding Memory Resource Management in VMware ESX 4.1.

There’s at least a third one that is worth a read: Enhanced VMware ESX 4.1 CPU Scheduler.

The 22-pages paper starts with a brief introduction on the role of the CPU scheduler and then goes on with an in-depth analysis of the design changes applied to ESX 4.1:

ESX 4.1 introduces wide-VM NUMA support, which improves memory locality for memory-intensive workloads. Based on testing with micro benchmarks, the performance benefit can be up to 11–17 percent.

In ESX 4, many improvements have been introduced in the CPU scheduler. This includes further relaxed co-scheduling, lower lock contention, and multicore-aware load balancing. Co-scheduling overhead has been further reduced by the accurate measurement of the co-scheduling skew and by allowing more scheduling choices. Lower lock contention is achieved by replacing the scheduler cell lock with finer-grained locks. By eliminating the scheduler cell, a virtual machine can get higher aggregated cache capacity and memory bandwidth. Lastly, multicore-aware load balancing achieves high CPU utilization while minimizing the cost of migrations.

It also includes an entire benchmark section with the performance evaluation of the updated design, comparing ESX 3.5 with ESX 4.

Spiceworks 5.0 to support Hyper-V

Spiceworks is a private US-based company founded in 2006 that offers a completely free system management platform for hardware/software/licenses inventory, change management, helpdesk, OS remote control and network mapping.

The company introduced support for VMware vSphere in version 4.6, released in March.

Now it’s the turn of Hyper-V: the upcoming release 5.0 will include support for the Microsoft hypervisor according to an official communication published earlier today by the company:

  • See all the virtual machine data on MS (& VMware) virtual servers as well as details like allocated RAM and hard disk space.
  • Start and stop your VMs when the need arises – allowing for more sophisticated virtualization management.
  • See and report changes over time for a VMs state and configuration
  • See all your VMs across all your hosts

The major update is planned for September. 
Well before that date Spiceworks 5.0 will be available as a public beta.

Service Pack 1 for Windows Server 2008 R2 won’t hit the market before H1 2011

Just a couple of weeks ago Microsoft opened the public beta program for the Windows Server 2008 R2 and Windows 7 Service Pack 1.

The update is especially interesting as it introduces two key technologies for virtualization: Dynamic Memory for Hyper-V and RemoteFX for Remote Desktop Services (RDS).
Earlier this year, widespread rumors suggested that the SP1 would arrive within the end of this year, but Microsoft recently published in its FAQ page, a different roadmap which places the update somewhere in H1 2011.
Mary Jo Foley at ZDNet is reporting the rumored date of April 2011.

Microsoft is trying to change the market perception about its capability to execute, fighting its fame of over-promising and under-delivering vendor, while surprising competitors at the same time. So it won’t be too surprising to see the SP1 indeed arriving before the end of this year.

CA relaunches its virtualization portfolio, hires former Director at VMware

In February, CA hired Andi Mann, the former Vice President of Research at Enterprise Management Associates (EMA) in February.
In his new role as Vice President of Product Marketing for Virtualization Management, Mann helped to reorganize the go-to-virtualization-market strategy.
virtualization.info also received a tip that CA hired Mike O’Malley, the former Director of Analyst Relations and Market Intelligence at VMware.
O’Malley is the Vice President of Product Marketing since January.

The two guys probably worked together at a plan to refresh the company’s image and credibility as a virtualization player.
The process culminated with the relaunch of the CA’s virtualization portfolio, which now includes five products, officially released yesterday:

Read more

Paper: The Design and Evaluation of a Practical System for Fault-Tolerant Virtual Machines

In May VMware published a very interesting paper describing the design of the Fault Tolerant (FT) feature, announced for the first time in late 2007 and shipped with vSphere 4.0 in June 2009.

The document, titled The Design and Evaluation of a Practical System for Fault-Tolerant Virtual Machines, also describes the alternative designs that VMware explored before selecting the actual one::

We have implemented a commercial enterprise-grade system for providing fault-tolerant virtual machines, based on the approach of replicating the execution of a primary virtual machine (VM) via a backup virtual machine on another server. We have designed a complete system in VMware vSphere 4.0 that is easy to use, runs on commodity servers, and typically reduces performance of real applications by less than 10%. Our method for replicating VM execution is similar to that described in Bressoud, but we have made a number of significant design changes that greatly improve performance. In addition, an easy-to- use, commercial system that automatically restores redundancy after failure requires many additional components beyond replicated VM execution. We have designed and implemented these extra components and addressed many practical issues encountered in supporting VMs running enterprise applications. In this paper, we describe our basic design, discuss alternate design choices and a number of the implementation details, and provide an evaluation of our performance for both micro-benchmarks and real applications.

Thanks to Yellow Bricks for the news.

VMware’s Memory Compression soon available for other hypervisors?

Last week VMware released vSphere 4.1, an impressive minor release for its virtual infrastructure which introduced a number of remarkable new features. One of them is called Memory Compression:

Compressed memory is a new level of the memory hierarchy, between RAM and disk. Slower than memory, but much faster than disk, compressed memory improves the performance of virtual machines when memory is under contention, because less virtual memory is swapped to disk.

See Understanding Memory Resource Management in VMware ESX 4.1 for more details.

While virtualization.info can’t say when the IT industry started researching the memory compression technique, we certainly can report about Nitin Gupta, a former member of the VMware’s Technical Staff part of the ESX Resource Management team from India, who mentioned memory compression on his personal blog in March 2009.

Read more

Symantec announces Workspace Virtualization 6.3 beta

Last week Symantec announced the Customer Preview for Workspace Virtualization 6.3.

Workspace Virtualization (formerly Software Virtualization Solution or SVS) is an application virtualization platform acquired from Altiris in January 2007.
Symantec didn’t publish any significant update for more than two years. Then, in August 2009, the company released the first rebranded build since the acquisition, jumping from version 2.1 to version 6.1.

In March the company released the Customer Preview of version 6.2 which introduced a new package format named XPF, containing both streaming and virtualization information so customers no longer had to convert a VSA into something that Workspace Virtualization can consume.

The new 6.3 Customer Preview instead introduces:

Read more

Paper: Understanding Memory Resource Management in VMware ESX 4.1

Last week VMware released a massive “minor” update for its virtual infrastructure platform.
vSphere 4.1 introduces a number of remarkable new features including what is called Memory Compression:

The idea of memory compression is very straightforward: if the swapped out pages can be compressed and stored in a compression cache located in the main memory, the next access to the page only causes a page decompression which can be an order of magnitude faster than the disk access. With memory compression, only a few uncompressible pages need to be swapped out if the compression cache is not full. This means the number of future synchronous swap-in operations will be reduced. Hence, it may improve application performance significantly when the host is in heavy memory pressure. In ESX 4.1, only the swap candidate pages will be compressed. This means ESX will not proactively compress guest pages when host swapping is not necessary. In other words, memory compression does not affect workload performance when host memory is undercommitted.

Read more

Training: Vyatta offers a free networking course for VMware and Citrix customers

Vyatta is now offering for free its Network Virtualization course, part of their Vyatta University training catalog.

The online course teaches how to install, verify and perform basic configuration of Vyatta OVF and XVA virtual appliances for adding routing and security to VMware ESX and Citrix XenServer.

You have to register to access, but considering that Vyatta is an open source router available for free, and that the course is free too, it may be well worth the effort.

Thanks to NTPRO.nl for the news.