Sorry for my rude title Scott but I was just on the phone with me ex Capgemini colleague Ernst Cozijnsen and we had a long discussion about super fast storage for replicas in a View environment. In the end we settled for RAM. I immediately jumped into my lab to setup a proof of concept to see how it performs and it’s pure awesomeness, faster than fast and quicker than quick. You want to see what we discussed? Well here’s the story. In the proof of concept I’m using a Windows 2008 64 bit Enterprise server with 7 GB of RAM and the StarWind iSCSI target software. I’ve configured this iSCSI target with a RAM disk of 6 GB and created a VMFS on the iSCSI target. I’ve cloned a Windows 2003 virtual machine to the newly created VMFS hosted in RAM and did some performance checks. I was astounded.

How to enable the Vmkernel System Info Shell (vsish) on ESX

In this article I want to set the record straight regarding last week’s article about New in esxtop RESV/s (SCSI reservations per second). During VMware Communities Roundtable Podcast number 118 with Krishna Raj Raja. I have learned that I didn’t measure the right metric with the correct method so now I’ve used the right method and metric -> CONS/s

In this video I’ll show you the new SCSI Reservation stats and the impact on the storage performance when the number if SCSI reservations becomes too high.

I’ve just recorded a real cool video which shows you how to install and configure ApplicationHA. This new product from Symantec and VMware is able to monitor applications within the virtual machine.

The VMware vCloud API provides support for developers who are building interactive clients of VMware vCloud Director using a RESTful application development style. vCloud API clients and servers communicate over HTTP, exchanging representations of vCloud objects. These representations take the form of XML elements. HTTP GET requests are used to retrieve the current representation of an object, HTTP POST and PUT requests are used to create or modify an object, and HTTP DELETE requests are typically used to delete an object.

In my previous post "Running the VMware vSphere Hypervisor stateless" I’ve explained how to setup an ESXi deployment server, but now we are going to take it one step further. To be able to save the ESXi configuration settings there’s a CCBoot feature available which is called “Write Back”. In this episode (HD) I’m going to show you how to enable “Write Back” for both the ESXi host and the CCBoot server. After rebooting the ESXI host the configuration will be preserved.

This video <- HD version - will show you how to create a stateless VMware vSphere Hypervisor formally known as ESXi and how to boot it trough PXE-iSCSI. Yesterday evening I finally succeeded in booting an ESXi 4.1 host with PXE and iSCSI. After firing the tweet, I’ve received a lot of responses asking me how I did it. In the video I’ll show you how to build your own staging server and the deployment of an ESXi 4.1 host. I’m not really a Linux guy so I had to create a Windows distribution server

vSphere 4.1 introduces a load-based teaming (LBT) policy that ensures vDS dvUplink capacity is optimized. LBT avoids the situation of other teaming policies in which some of the dvUplinks in a DV Port Group’s team were idle while others were completely saturated just because the teaming policy used is statically determined.

In this video I’ll show you how you use the VI Client user interface to deploy the CapacityIQ appliance. VMware distributes the appliance as a .zip file that includes an Open Virtualization Format (OVF) file. After the import the CapacityIQ OVF file, I’ll also show you how to configure the virtual appliance.