2V0-622 · Question #130
An administrator is troubleshooting a virtual machine that has unexpectedly powered off. Which two logs should be used to troubleshoot the issue? (Choose two.)
The correct answer is A. vmware.log B. hostd.log. vmware.log records per-VM events and hostd.log records host daemon operations, making both the primary logs for diagnosing an unexpected virtual machine power-off.
Question
An administrator is troubleshooting a virtual machine that has unexpectedly powered off. Which two logs should be used to troubleshoot the issue? (Choose two.)
Options
- Avmware.log
- Bhostd.log
- Csyslog.log
- Dshell.log
How the community answered
(24 responses)- A83% (20)
- C13% (3)
- D4% (1)
Why each option
vmware.log records per-VM events and hostd.log records host daemon operations, making both the primary logs for diagnosing an unexpected virtual machine power-off.
vmware.log is stored in the VM's working directory and captures all VM-level events including power state transitions, VMX process messages, and hardware errors that directly indicate why the VM powered off unexpectedly.
hostd.log is the ESXi host daemon log that records all host management operations including VM power actions initiated by vCenter, users, or automated processes, making it essential for correlating external triggers with the power-off event.
syslog.log captures general ESXi kernel and operating system messages and is not the primary source for VM-specific power state change events.
shell.log records commands entered in the ESXi shell by administrators and has no relevance to diagnosing an unexpected virtual machine power-off.
Concept tested: ESXi log file identification for VM troubleshooting
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-832A2618-6B11-4A28-9672-93296DA931D0.html
Topics
Community Discussion
No community discussion yet for this question.