System Administrator

Snapshots fail to merge with error 0x80070070 Applies to: Windows Server 2008, Windows Server 2008 R2  Error: Snapshots fail to merge with error Cause: Low disk space.

This document provides installation procedure, usage, and support information for Dell OpenManage systems management on VMware ESXi Server software. Download and Install VMware vSphere CLI Download and Install VMware vSphere CLI (VMware-vSphere-CLI-4.0.0-198790) from VMware website ( www.vmware.com ) Download and Install Dell OpenManage Offline Bundle and VIB for ESXi Request you to follow below instructions to install the Dell OpenManage Offline Bundle and VIB for ESXi

Symptoms: Recently we have been experiencing problems with ESXi 4.1 hosts becoming disconnected from vCenter. Troubleshooting Steps: - vMotion fails at 67%. Error message is ‘The VM failed to resume on the destination during early power on” hostd will post the below events on the destination ESXi host:

We have normal scenario such as DC got crashed or rebooted and many other cause to have  the common steps that we can do health checks on domain controllers.  we normally do AdminPrep which is not a right thing as of now. I”ll post some health check stuff here.  which you guys can go through and come back if what else can be done on this DC if got crashed or rebooted state.

Cause: Recently we have been experiencing problems with ESXi 4.1 hosts becoming disconnected from vCenter. Troubleshooting Steps: 1.       Right clicking on the host and selecting Connect does not normally fix the problem. Also logging in directly to the host with the vSphere Client usually does not work, or if it does it disconnects quickly after connecting. 2.      All of the virtual machines running on the host continue to run; however without the host being connected to vCenter or being able to connected directly with the vSphere Client you are unable to manage the virtual machines. Also, connecting to the host with PowerCLI does not work, if it does connect it drops the connection soon afterwards.

For servers without CD drive or remote KVM you might want to use an USB Flash Drive to install ESXi to the hardware. This post explains how to create a bootable ESXi Installer USB Flash Drive in less than 2 minutes. The Flash Drive will work totally identical to an Installable CD. There are many USB Flash drive bootable software like in microsoft we have windows 7 USB/DVD download tools, here I have took Rufus tool for example. Download  Rufus Download  or  create  an ESXi Image Connect the USB flash drive to your computer Open Rufus Select your Device Select your ISO file Select  MBR partition scheme for BIOS or UEFI computers Press  Start Select  Yes  when it asks to replace menu.c32. Rufus will now create your bootable ESXi Installer USB Flash Drive. This will take about one minute. Additional Hint When you boot a server with this USB Flash Drive the ESXi Installer will copy the whole installer to the memory...

On daily basis we face lots of connectivity issue on virtual machine and here some troubleshooting hints to find/fix the issue. Disconnected A virtual machine is marked as disconnected when the vCenter has lost communication to the ESXi host where the virtual machine is running. The host is marked as not responding. This state is usually caused by a host that has been crashed. Other reasons could be network issues or problems with the vpxa service running on the host. In this state vSphere HA would usually comes into play and tries to restart the virtual machine on another host in the cluster. Solution You can quickly reproduce that state by stopping vpxa (~ # /etc/init.d/vpxa stop) Inaccessible A virtual machine is marked as inaccessible when the host can no longer access the virtual machine configuration (.vmx) file. Solution That state can be caused by problems with the storage array or a renamed folder in the datastore. When there is no issue wit...

The following log files contain information that needs to be track on a VMware vSphere ESX Host to be in compliance with many security standards and best practices We can also use syslog or splunk lightweight forwarders for this purpose. /var/log/vmkernel /var/log/secure /var/log/vmkwarning /var/log/vmksummary /var/log/vmksummary.txt /var/log/messages /var/log/vmware/*.log /var/log/vmware/aam/*.log /var/log/vmware/aam/*.err /var/log/vmware/webAccess/*.log /var/log/vmware/vpx/vpxa.log /vmfs/volumes/*/*/*.log Table with Explanation of files to log for VMware vSphere ESX Component Location Purpose   VMkernel   /var/log/vmkernel   Records activities related to the virtual machines and ESX VMkernel warnings /var/log/vmkwarning Records activities with the virtual machines VMkernel summary /var/log/vmksummary Used to determine uptime...

If VMware HA doesn’t work. Verify that host name is lowercase: hostname; hostname -s Verify that host name in /etc/hosts is lowercase Verify that search domain in /etc/resolv.conf is in lowercase Verify that host name in /etc/sysconfig/network is fqdn, all lowercase Verify that the host name in esx.conf is fqdn, all lowercase Verify that host name in DNS is lowercase: nslookup; <short hostname> (should properly resolve fqdn of host, all lowercase) Verify that all primary service consoles have the same name. Verify that all primary service consoles are in the same IP subnet. If VMotion vmkernel port is on same vSwitch as primary service console, use das.allowVmotionNetworks=1 If host has multiple service consoles, use  KB 1006541  and the das.allowNetwork0 HA option to ensure that only the primary service console is allowed. Verify that customer has appropriate licensing for HA, and has available licenses:  In LM Tools, perform a status inquiry, verify ...

I recently bought a WD external drive to be used on my laptop for VMware workstation and the idea being that all shared files  and VM's i can load it in the movable drive. Scenario:  loaded the VM in the WD drive. launched VMware player - create a vm to an existing VM. after mounting the VM by double clicking the .vmx file. VM Player kicks in and starts to load, but then the following error was thrown: Here’s how to fix it: Edit your .vmx file with your favorite text editor Add a line to the end of this file: diskLib.sparseMaxFileSizeCheck="FALSE" Now fire up the VM again and hopefully it should work as normal!