Browsing Posts tagged ESXi

Some years ago, I’ve write some posts on how install Dell OpenManage on VMware ESXi. The OpenManage Server Administrator (OMSA) is a Dell tool really useful for a central management or to be integrated in other Dell’s management tools. There are different options, but basically the most used ways are: Use the Dell ESXi custom image that already include also a version of OMSA (not necessary the latest) Use the command line Use VMware Update Manager The last option is my preferred option because is really faster and simplest.

I’ve got a case of a host upgraded to VMware vSphere 5.1 with a determinist PSOD during each host reboot or shutdown (I’ve found the issue during the first patch update). No difference if hosts where rebuild from scratch with a similar configuration. And no difference with all recent ESXi patches. After a full upgrade of each BIOS, firmware and drivers (and of course the HCL verification) I’ve only found the KB 2038281 (ESXi 5.1 host fails with a purple diagnostic screen when Beacon probing is enabled). Syntoms where similar: Cannot reboot a ESXi 5.1 […]

I’ve read some posts (see in the bottom of this post for the references) and I notice how the  hypervisor comparison and choosing criteria are still a interesting trend and not only a marketing battle between different vendors (and maybe there will be more interest will be on this aspects with the release of Windows Server 8). But in several cases the comparison is limited to the hypervisor technical characteristics (and I’ve already written something about Hyper-V 3.0, XenServer 6.0 and RHEV 3.0) without considering (except in some cases) that the those are only one […]

In ESXi the partitions schema is automatically defined by the installation process and there is no way to modify it (you can only choose where install the hypervisor). There is a great post from Rickard Nobel (ESXi 5 partitions) that explain the structure of the partitions, their size and their purpose. But it does not explain how to get this information. To see the partition layout in ESXi 5, the fdisk command will not work on new GTP disk (this type is used for all new disks and for disks that are extended to more […]

There is an performance monitor at VM level that show always a null value: it’s the VM Power Graph. The same monitor at host level show the power usage of the specific host. But by default, the power usage of the VMs are not calculated. To enable this experimental feature you must change an advanced parameter (Power.ChargeVMs) on each host (by default, as show in the picture, is zero… it must be changed to 1):

In a vSphere upgrade process, there are two different approach for the host upgrade: a fresh re-install or a in-line upgrade. In the VMware site there is an interesting post about this choice. The differences between an upgraded host and a freshly installed host are:

Source: VMware vSphere 4.1 Update 2 Released The VMware vCenter Server 4.1 Update 2 release offers the following improvements: Support for new processors: vCenter Server 4.1 Update 2 supports hosts with processors on AMD Opteron 6200 series (Interlagos) and AMD Opteron 4200 series (Valencia). Note: For the AMD Opteron 6200 and 4200 series (Family 15h) processors, vCenter Server 4.1 Update 2 treats each core within a compute unit as an independent core, except while applying licenses. For the purpose of licensing, vCenter Server treats each compute unit as a core. For example, although a processor […]

© 2017 © 2013 vInfrastructure Blog | Hosted by Assyrus