The Virtualization Practice

1059 search results for "vmware"

HyTrust has announced Series B Financing in the amount of $10.5 Million with participation from Cisco, Granite Ventures as well as existing investors Trident Capital and Epic Ventures. This is very good news for HyTrust. While the Series B Funding was not much of a surprise given that HyTrust fits into the Virtualizaiton Security within its own niche. What is surprising is that Cisco is one of the backers of this innovative product.

When I first interviewed Reflex System’s CEO he had a desire for the vTrustTM VMsafe-Net driver be the defacto standard for all such VMsafe-Net drivers. While others may not agree with this desire and will create their own VMsafe-Net drivers, TippingPoint is the first to integrate into Reflex’s VMC product to leverage the vTrust VMsafe-Net Driver and puts Reflex System’s on the second step of the path for vTrustTM to be the defacto standard. At the same time TippingPoint adds an Intrusion Protection System to the Reflex System VMC family of products with Tipping Point vController.

HyTrust

HyTrust is the Cloud Security Automation company. Its virtual appliances provide the essential foundation for cloud control, visibility, data security, management and compliance. HyTrust mitigates the risk of catastrophic failure and data breaches — especially in light of the concentration of risk that occurs within virtualization and cloud environments. Organizations can now confidently take full…

Virtualization Aware APM Advances

We categorize the vendors that do performance and availability monitoring for virtualization and cloud computing into four categories: Resource and Availability Monitoring – This is primarily about taking data from the hypervisor vendor (most often the VMware vCenter API data), storing it, trending it, reporting on it, analyzing it, and alerting on it. Infrastructure Performance…

In a slightly strange “didn’t they already have Xen in the kernel” kind of way, Novell has certified Suse Linux Enterprise Server as a “perfect guest” running on Citrix XenServer, allowing joint support of the combined solution. The deal is asymmetric (it wouldn’t really make sense to run XenServer on SLES) but it reflects an open approach characteristic of the way Novell operates, in embracing the reality that customers will want to use one of a number of possible hypervisors, and that Novell has to get along with everyone. In return Novell is starting to push it’s PlateSpin Recon product through the Citrix channel.

The grid approach to desktop virtualization, offered by vendors like Kaviza and Synchron offers several advantages in terms of cost and flexible use of hardware resources. The cost savings come from not requiring a SAN. The implications of no SAN are no VMotion, no HA and no DRS. However Citrix XenApp has proven that user and application centralization can be effectively managed without these features.

Project Virtual Reality Check have released their Phase 2 white paper on Terminal Server/RDS workloads running on the latest generation Intel processor: the Xeon 5500 series (Nehalem). Besides providing some great figures to support the adoption of Intel’s Nehalem to drive high demand virtualized workloads, this is an interesting and important comparison document for those considering centralised desktop virtualisation.

Aimed for those who use medium sized storage for virtualization loads, Virsto will add quite a bit of needed functionality to Hyper-V to reduce disk space requirements, improve general disk IO performance, as well as provide faster high availability failover. The disk space saving Linked Clone technology available for VMware ESX and ESXi has been missing from Hyper-V, Virsto provides this.

Rethinking vNetwork Security

Brad Hedlund of Cisco asked the question, should the physical network security policy be different than the virtual network security policy? The answer is obviously no, but why are they treated separately? I and other have pushed the concept that to gain performance, redundancy, and security that you should use multiple network links to your virtualization host to separate traffic. However, does this really give you security?