Tag Archives: vSphere

vSphere ESXi 4.1 + EMC VNX – ALUA – NOT THE DEFAULT!

One of the changes in the VNX platform from the previous generation EMC storage arrays is that the Failover Mode 4 is supposed to be the new default. And I say “supposed to be” because during the beta program, I did not find that this was the case. The ESXi hosts we connected in to […]

“SOON TO BE RELEASED” TREND MICRO IMSVA8.0 = BEST OF ALL WORLDS!

Wow! I should change “released” to say “soon to be unleashed upon the world” !!! Trend Micro has done it AGAIN – hitting the ground running this year – easily outpacing most of the competition in the race to win the cloud-enabled anti-malware software market. From cloud-enabled, VDI-aware endpoint protection, to vmsafe API-based virtual machine […]

VMware vSphere 4.1 – NETWORK I/O CONTROL

Another new feature introduced with vSphere 4.1 that doesn’t seem to get any "coverage" is Network I/O Control (NetIOC). Very similar to the I/O Control introduced for storage, NetIOC uses shares and hard limits to determine who gets access to the network resource (bandwidth). When moving to 10Gb ethernet, it’s common to see substantially fewer […]

vSphere 4.1 – LOAD BASED TEAMING

One new "feature", or probably better described as an enhancement, introduced in vSphere 4.1 is Load Based Teaming. Briefly, Load Based Teaming takes the traditional three load balancing choices (route based on originating virtual Port ID, IP hash, or Source MAC) and offers a dynamic, "on-the-fly" policy for better utilization of bandwidth.

VMware PERFMON DLLs

One of the little known/used enhancements from the upgrade to vSphere (and the accompanying VM Tools update) is the in-Windows perfmon DLLs. See image below–

CPU SCHEDULING IN vSPHERE 4

 In ESX 4, many improvements have been introduced in CPU scheduler. This includes further relaxed co-scheduling, lower lock-contention, and multi-core aware load balancing. Co-scheduling overhead has been further reduced by the accurate measurement of the co-scheduling skew, and by allowing more scheduling choices. Lower lock-contention is achieved by replacing scheduler cell-lock with finer-grained locks. By […]

ESX4 WITH INTEL NEHALEM AND AMD ISTSANBUL PROCESSORS

VMware has made a significant change that when used in conjunction with the latest intel (Nehalem) or AMD (Istanbul) CPU can take a one vCPU VM performance to a new height.  http://blogs.vmware.com/performance/2009/09/comparing-performance-of-1vcpu-nehalem-vm-with-2vcpu-harpertown-vm.html

vMOTION FAILS AFTER UPGRADE FROM 3.X TO 4.X

Did you forget about all the fancy CPU masking you did in version 3.x to get vMotion to work across different CPU revisions.  Well if you did you may run into this when you upgrade. You can reference VMware Knowledgebase article 1011294 when calling VMware support if the resolution does not work.

Archives

WP-Backgrounds Lite by InoPlugs Web Design and Juwelier Schönmann 1010 Wien