New finding while trying to import the existing virtual machine from ESX 3.5 to vSphere 4 ESX host. I got an image from previous ESX 3.5 which is running hardware version 4. I was trying to import it to the new ESX 4.0 through the import wizard, and been failed for couple of times. During the wizard, it allow you to change the virtual machine name, thin provision, disable unnecessary services and upgrade to virtual hardware version 7. I had selected the necessary configuration but non of it were success. It had always failed at the stage of 12 % during the import process. I even had browse the datastore to monitor the progress, for unknown reason, the task will be failed for no reason, which not even a packet was drop during the process.
Read more »
In 1 of the demo video, I had seen the storage vMotion performance significant improve as much as 25% of the time and reduce the storage processor overhead at roughly 20% which offload the ESX performance during the storage vMotion execution. Previously, you may aware that the storage vMotion will usually take a long time and consume a lot of resource from Host & Storage. With vStorage API Array Integration, you will able to offload this to the storage array to handle directly which reduce the system overhead from ESX host itself.
Here is the option to turn on or off the VAAI, Value of Zero meant off, and 1 refer to ON.
Read more »
VMware vSphere 4.1 was release on 13 July 2010 last week. VMware vSphere 4.1 introduced an impressive number of new features and new licensing format.
The following is complete VMware vSphere 4.1 license comparison chart.
click to enlarge.
Read more »
To support VLANs for VMware Infrastructure users, the virtual or physical network must tag the Ethernet frames with 802.1Q tags using virtual switch tagging (VST), virtual machine guest tagging (VGT), or external switch tagging (EST). If you’re looking for how to configure VLAN tagging in VMware vSphere, you may refer to VMware KB 1004074 & KB 1004252.
Last week I have configured a VLAN tagging on one of my vSphere 4 Update 2 cluster and due to some reason, I have remove the VLAN ID manually.
Read more »
With the VMware vSphere 4.1 release, VMware had officially supported the Windows 2008 R2 with the latest release of the official document. It had taken such a long period for VMWare to officially announce in the compatibility matrix documentation.
Please find the full information from here.
Read more »
