The root cause stems from a January 2009 VMware patch: ESX350-200901401-SG. Other applications that perform snapshots can cause the behavior, such as the product I’m using: Veeam Backup 3.0.
Run vmtools mac Patch#
However, on hosts installed with the patch bundle ESX350-200901401-SG, the VMware Tools status on the virtual machines may stay as Not Running even after the VCB operation completes.Īlthough the KB article specifically ties the problem to VCB, the problem is not limited to VCB in my experience. Mind you, I’m not running VCB in the lab (thank God and Veeam), however, the description in the KB article mostly matched my situation.ĭuring the normal VMware Consolidated Backup (VCB) operation, the VMware Tools status changes from OK to Not Running for some time during the initial snapshot operation, but it returns to OK after the VCB operation completes. It was then that I noticed VMware Tools status was showing “Not Running” for a whole slew of other VMs which I knew had tools installed.Ī quick search uncovered a recently updated VMware KB article 1008709 “ VMware Tools status shows as not running after running VMware Consolidated Backup“. Even stranger, when I went back to the VIC, the VMware Tools status now showed “Tools OK”. I logged into the VM and strangely enough, the VMware Tools were installed and the VMware Tools service was running. Unfortunately the graceful shutdown and restart options were grayed out which is a good indicator that the VMware Tools are not installed or not running. While in the Virtual Infrastructure Client (VIC), I attempted to perform a graceful shut down on a VM by right clicking on it and choosing Shut Down Guest. I ran into an disturbing problem this evening in the lab.
0 kommentar(er)
