"scoreboard file is not readable" Error Occurs for the VM that have not been changed its VM Name
Article ID: 406658
Updated On:
Products
Issue/Introduction
The KB article linked below describes that the "scoreboard is not readable" error can occur when the VM name has been changed.
- scoreboard is not readable error
However, you may also encounter this error every two minutes on the VMs whose names have never been changed before.
|
/var/run/log/hostd.log ####-##-##T##:##:## Wa(164) Hostd[2101045]: [Originator@6876 sub=VMXStatsProvider(0000007e4569c7d0)] Adding VM 10 failed, file /vmfs/volumes/datastore/vmname/vmname.scoreboard is not readable |
Environment
VMware ESXi 8.0 U3
Cause
The error log can be generated when a VM is deployed from a template. If you enter a VM Name different from the template source VM Name, the scoreboard file is created based on the template source VM, not the newly deployed VM.
The VMX stats for these VMs won't be added to the host stats registry, but they will still be saved in each VM's scoreboard file.
Resolution
Currently there is no solution. This will be fixed in the future release
The error log itself does not cause any issues for running VMs.
Workaround:
1) Disable the scoreboard configuration before creating a template.
2) Modify the scoreboard file name.
2-1) Without VM Power Off
- From ESXi Host Client UI, Edit VM Settings -> VM Options -> Advanced -> Edit Configuration
- Empty the value for "vmxstats.filename" to "". --> vmxstats.filename = ""
- Save the settings, and vMotion the VM so that it creates a new scoreboard file with the current VM Name.
- After the vMotion, delete the old scoreboard file manually.
2-2) With VM Power Off - scoreboard is not readable error
|
Feedback
