2V0-621 · 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. When a virtual machine powers off unexpectedly, the VM-level log and the host daemon log together provide the most relevant evidence for root-cause analysis.
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
(22 responses)- A73% (16)
- C9% (2)
- D18% (4)
Why each option
When a virtual machine powers off unexpectedly, the VM-level log and the host daemon log together provide the most relevant evidence for root-cause analysis.
vmware.log is the per-virtual-machine log file located in the VM's working directory; it records every power state transition, VMX events, and hardware emulation errors, making it the primary source for understanding why a VM powered off unexpectedly.
hostd.log is the ESXi host daemon log that records all management-plane operations including VM power actions initiated by the host, task completions, and host-side errors that can trigger an unexpected power-off event.
syslog.log captures general ESXi kernel and system messages and is useful for host-level issues, but it does not contain VM-specific power event details with the granularity needed to diagnose an unexpected VM shutdown.
shell.log records interactive SSH and ESXi Shell commands entered by administrators and does not capture automated VM power state changes or hypervisor-initiated shutdowns.
Concept tested: VMware log files for VM power-off 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.