While vCloud director is the hot topic now for private cloud computing solution from VMware, some of us may overlook into certain requirements that may require Site Recovery Manager for DR solution. If you run in to this situation, the current version of vCloud director may not be the option for you. SRM are officially not supported with vCloud director, which been informed during the official training class and the official reference document you can read from here. You may want to wait for the update release in the future if you plan to have SRM in your private Cloud environment with vCloud director.
Read more »
We were doing some stress test with more than 15 VMs on a single B250M2 Cisco UCS blade machine with 2 x Intel 6 Cores 2.93Ghz, and 192GB memory. While are stress test are pretty simple, each VM been provisioned with 2 vCpu and 4GB of physical memory. We maximize the CPU load of all the virtual machine and end up I was able to capture the print screen as attach here.
Read more »
As you may aware, significant improvement had been done on the latest hypervisor from VMware vSphere 4.1.
1 of the key changes are the vCPU for each virtual machine with latest NUMA hyperthreading architecture.
I found a very details and great post talk about this topic, please read the full post from here.
This will significant improve the Consolidation ratio and performance over the virtual machine VS the previous version ESX 4.0.
Read more »
For the past 1 week, I have been busy with the APC PCNS and ESXi 4.1 and I would like to share my experience “How to make APC PCNS 2.2.4 work with ESXi 4.1″ here.
Basically I will not discuss How To Install PowerChute Network Shutdown on VMware ESX /ESXi again and you may refer to APC official link here.
If you’re try to install APC PCNS 2.2.4 on vSphere Management Assistant (vMA) 4.1 and I’m sure you will get the similar error like “This version of PowerChute Network Shutdown only support VMware ESXi” which I think APC teams should it much more clear. The error message caused by APC PCNS (ver 2.2.4) setup file – “install.sh” which check on “/etc/vima-release” file. In the vMA 4.1 released, you’re can only found “/etc/vma-release” file which changed recently. Create a symbolic link or edit the installation script can temporary ignore these error message. See this link.
Read more »
If you are deploying nexus 1000v in your VMware vSphere environment, you may usually hit to the point require to unload VEM, VSM or reconfigure. Today I found some tips just to share here. If you accidentally deleted your VSM which before you unload the VSM from the vCenter, you will either end up having orphan nexus 1000V show up in your vCenter. Even if you try to name the same as previous, it will prompt the error telling you that the previous extension key and your current extension are mismatch.
Read more »
