Skip to main content

openQRM 3.5 released: Control your heterogenous virtualization jungle

Qlusters is pleased to announce the contribution of openQRM 3.5 open source release to the openQRM SourceForge project. The 3.5 open source release succeeds release 3.1.4 and includes a set of new features based on input from various datacenters and test/dev labs. Release 3.5 is available for download now.

It has been pleasing and rewarding to see the openQRM project grow rapidly since its launch in January 2006, including winning SourceForge’s “Project of The Month” in July 2006. The 120,000 downloads to date are the basis for numerous openQRM implementations in datacenters globally, and the many articles published in the industry discussing openQRM have established it as one of the leading open source solutions for systems provisioning and management.

Following release 3.5 – the last release from Qlusters – we hope the community will continue to evolve and develop openQRM together with Matt Rechenburg – openQRM’s active project manager, who has been doing a wonderful job not just in driving the community but also in evangelizing and promoting openQRM throughout the industry. Qlusters would like to wish the openQRM project community, and Matt Rechenburg, a future of prosperity and continued success.


Here's the announcement!

and download the Virtual Data Center Appliance version 3.1 here!

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...