Virtual machines, containers, functions. Market knowledge for IT decision makers since 2003
virtualization.info Editors 
Mark Pileski, former Vice President of Marketing at VMLogix, just left the company to take the same role at I Love Rewards.
Pileski came from PlateSpin, where he was Director of Marketing before the Novell acquisition. He remained at Novell for less than a year and then moved to VMLogix in May 2008.
Apparently, VMLogix didn’t replace Pileski yet as the only executive listed on the Leadership Team page, excluding the CEO and the CTO, is the Worldwide President of Sales.
In September 2008 a new US startup called BlueBear entered the virtualization space, previewing a promising management console, Kodiak, able to support VMware ESX, Citrix XenServer and Microsoft Hyper-V hypervisors.
Unfortunately, in more than two years, the company didn’t manage to deliver at least version 1.0 of Kodiak, and eventually went out of business.
Microsoft is increasing its marketing effort in promoting its VDI platform since a few months now.
In early April the company published a bunch of Microsoft publishes Deploying Personal Virtual Desktops guides. Now it’s time for the Deploying Remote Desktop Connection Broker with High Availability paper.
The 23-pages step-by-step guide describes how to configure Remote Desktop Connection Broker (RD Connection Broker) in a Windows Server 2008 R2 Enterprise or Windows Server 2008 R2 Datacenter failover cluster, as part of a configuration that provides users with access to personal virtual desktops or virtual machines in a virtual desktop pool through RemoteApp and Desktop Connection.
After more than one year since the last version, Veeam releases this week version 4.0 of its performance reporting tool for VMware vSphere: Reporter (formerly Reporter Enterprise).
Reporter 4.0 introduces a number of new features:
Yesterday Oracle released a new update for its hosted desktop virtualization platform VirtualBox, which is now officially called Oracle VM VirtualBox.
Version 3.2, in public beta since March, introduces a number of remarkable new features:
virtualization.info already reported about several aspects (features, GA availability and strategy) of the new Citrix client hypervisor launched two weeks ago at Synergy 2010 (see event coverage).
Now, while additional feedbacks about the release candidate are being published by early adopters, and while Citrix is busy answering VMware on the value of client hypervisors for BYOC models, we are able to share additional details about its internals.
During the conference in fact, Ian Pratt (Chairman of Xen.org and Vice President of Advanced Virtualization Products at Citrix) and Tom James (Desktop Virtualization Manager of Business Client Platform Division at Intel) shared interesting details about the XenClient and Synchronizer internals.
Open Virtual Switch (or Open vSwitch) is the open source answer (supported and sponsored by Citrix) to the Cisco Nexus 1000V and the VMware vNetwork Distributed Switch architecture.
Citrix announced the project in June 2009, but the early, public lines of code didn’t appear before August.
It took almost one year to move from version 0.90.4 to version 1.0, which introduces a number of features:
Last week, during its Synergy 2010 conference (see virtualization.info coverage), Citrix announced the availability of XenServer 5.6.
This is the first update since Citrix decided to release XenServer as a free and open source hypervisor in February 2010, and with it Citrix completely changed the naming convention for the product.
The stand-alone product called Essentials for XenServer doesn’t exist anymore: the enterprise management capabilities that it offers have been integrated in the XenServer package, and distributed across four different editions: Free (the one fully open source), Advanced, Enterprise and Platinum.
|
|
|
|
When VMware announced the VMsafe APIs more than two years ago, virtualization.info praised the effort and suggested that the advent of the technology was the best thing ever happened to the security industry in a long time. It could have been, assuming a solid strategy behind it, and a proper execution.
But more than two years later, it’s safe to say that VMsafe has gone nowhere so far and that the execution of the strategy has been all but flawless.
This may well depend on the incapability of VMware to approach the security world (their ACE product has been a colossal fiasco that still exists only because it’s being super-slowly integrated into Workstation for free), but the company is not the first one to blame for this failure.
Security vendors in fact did nothing so far to secure virtual infrastructures in a proper, more effective and efficient way.
A large-scale, concrete adoption of hardware virtualization platforms can be tracked back to 2006 so, even accepting that security vendors have been careful in approaching the emerging technology, it’s still true that they had four years to do something. Instead, in 2010, top players like McAfee, Symantec, TrendMicro, and a myriad of smaller others, have yet to address the customers need for security in the virtual data centers.
Worse than that, hardware virtualization is facilitating the advent of Infrastructure-as-a-Service (IaaS) cloud computing platforms, where the security challenges are even bigger, and the security vendors above haven’t demonstrated any commitment on these platforms at all.
Earlier this week, Citrix unveiled the public Release Candidate of its client hypervisor XenClient, beating on time VMware and its upcoming Client Virtualization Platform (CVP).
The VMware’s reaction has been instantaneous: the day after the announcement, the company released an article about the Bring Your Own Computer (BYOC) IT governance model, claiming that its current approach is way better and the real one.
Like Citrix in fact, VMware delayed multiple times the release of its client hypervisor, at the point that the upcoming release 4.5 of View, will not include it, as many have hoped.
VMware rather preferred to remove the experimental label from an existing feature of View Client for the so-called offline VDI scenarios that is simply called Local Mode.
