Scoreboard files are only used for VM statistics, and not for snapshots. These files are not mandatory, but they don't clear automatically. For example, you may see files similar to the following in the VM's folder:
/vmfs/volumes/datastore/vm_folder/
└─$ ll | grep scoreboard
-rw-rw-r-- 8.0K Dec 11 2024 vm_name-1.scoreboard
-rw-rw-r-- 8.0K Mar 25 2025 vm_name-2.scoreboard
-rw-rw-r-- 7.3K Apr 17 2025 vm_name-3.scoreboard
-rw-rw-r-- 7.3K May 27 09:18 vm_name-4.scoreboard
-rw-rw-r-- 7.3K Aug 1 11:43 vm_name-5.scoreboard
-rw-rw-r-- 7.3K Sep 5 16:47 vm_name-6.scoreboard
-rw-rw-r-- 7.3K Oct 15 19:03 vm_name-7.scoreboard
-rw-rw-r-- 7.3K Oct 17 13:31 vm_name.scoreboard
vSphere 8.x
vSphere 7.x
Every time a VM is powered on, migrated, suspended, or resume a new scoreboard file is generated. This behavior is normal.
/vmfs/volumes/datastore/VM_name/vmware.log
vmware.all:2024-10-23T17:13:48.067Z No(00) vmx - ConfigDB: Setting vmxstats.filename = "VM_name.scoreboard"
vmware.all:2024-10-23T17:13:48.167Z In(05) vmx - VMXSTATS: Successfully created stats file 'VM_name.scoreboard'
vmware.all:2024-10-23T17:13:48.168Z In(05) vmx - DICT vmxstats.filename = "VM_name.scoreboard"
vmware.all:2024-11-21T20:32:20.133Z In(05) vmx - VMXSTATS: Successfully created stats file 'VM_name.scoreboard'
vmware.all:2024-11-21T20:32:20.133Z In(05) vmx - DICT vmxstats.filename = "VM_name.scoreboard"
vmware.all:2024-12-11T14:41:08.197Z In(05) vmx - VMXSTATS: Successfully created stats file 'VM_name.scoreboard'
vmware.all:2024-12-11T14:41:08.198Z In(05) vmx - DICT vmxstats.filename = "VM_name.scoreboard"
vmware.all:2025-03-05T09:10:21.376Z In(05) vmx - VMXSTATS: Successfully created stats file 'VM_name.scoreboard'
vmware.all:2025-03-05T09:10:21.377Z In(05) vmx - DICT vmxstats.filename = "VM_name.scoreboard"
vmware.all:2025-03-25T14:14:39.053Z In(05) vmx - STATSFILE: StatsFile '/vmfs/volumes/adatastore/VM_name/VM_name.scoreboard' created
vmware.all:2025-03-25T14:14:39.054Z In(05) vmx - DICT vmxstats.filename = "VM_name.scoreboard"
vmware.all:2025-04-17T09:56:53.570Z In(05) vmx - STATSFILE: StatsFile '/vmfs/volumes/adatastore/VM_name/VM_name.scoreboard' created
vmware.all:2025-04-17T09:56:53.571Z In(05) vmx - DICT vmxstats.filename = "VM_name.scoreboard"
vmware.all:2025-05-27T08:17:35.292Z In(05) vmx - STATSFILE: StatsFile '/vmfs/volumes/adatastore/VM_name/VM_name.scoreboard' created
vmware.all:2025-05-27T08:17:35.292Z In(05) vmx - DICT vmxstats.filename = "VM_name.scoreboard"
vmware.all:2025-08-01T10:40:05.438Z In(05) vmx - STATSFILE: StatsFile '/vmfs/volumes/adatastore/VM_name/VM_name.scoreboard' created
vmware.all:2025-08-01T10:40:05.439Z In(05) vmx - DICT vmxstats.filename = "VM_name.scoreboard"
vmware.all:2025-09-05T15:41:35.478Z In(05) vmx - STATSFILE: StatsFile '/vmfs/volumes/adatastore/VM_name/VM_name.scoreboard' created
vmware.all:2025-09-05T15:41:35.478Z In(05) vmx - DICT vmxstats.filename = "VM_name.scoreboard"
vmware.all:2025-10-15T18:04:30.972Z In(05) vmx - STATSFILE: StatsFile '/vmfs/volumes/adatastore/VM_name/VM_name.scoreboard' created
vmware.all:2025-10-15T18:04:30.972Z In(05) vmx - DICT vmxstats.filename = "VM_name.scoreboard"
vmware.log:2025-10-15T18:04:30.972Z In(05) vmx - STATSFILE: StatsFile '/vmfs/volumes/adatastore/VM_name/VM_name.scoreboard' created
vmware.log:2025-10-15T18:04:30.972Z In(05) vmx - DICT vmxstats.filename = "VM_name.scoreboard"
For example on the above VM, the Guest OS reset (Guest OS restart)
2025-04-10T18:15:26.590Z In(05) vcpu-0 - Chipset: The guest has requested that the virtual machine be hard reset.
2025-04-17T09:56:51.961Z In(05) vmx - Hostname=esxihost.example.com
2025-04-17T09:56:53.570Z In(05) vmx - STATSFILE: StatsFile '/vmfs/volumes/Datastore/VM_name/VM_name.scoreboard' created
2025-04-17T09:56:53.791Z In(05) vmx - Chipset version: 0x13
2025-05-07T22:08:27.383Z In(05) vcpu-0 - Chipset: The guest has requested that the virtual machine be hard reset.
2025-05-27T08:17:34.115Z In(05) vmx - Hostname=esxihost.example.com
2025-05-27T08:17:35.292Z In(05) vmx - STATSFILE: StatsFile '/vmfs/volumes/Datastore/VM_name/VM_name.scoreboard' created
2025-05-27T08:17:35.531Z In(05) vmx - Chipset version: 0x13
2025-06-10T18:14:58.095Z In(05) vcpu-0 - Chipset: The guest has requested that the virtual machine be hard reset.
2025-08-01T10:40:05.034Z In(05) vmx - Hostname=esxihost.example.com
2025-08-01T10:40:05.438Z In(05) vmx - STATSFILE: StatsFile '/vmfs/volumes/Datastore/VM_name/VM_name.scoreboard' created
2025-08-01T10:40:05.568Z In(05) vmx - Chipset version: 0x13
2025-09-05T15:41:34.128Z In(05) vmx - Hostname=esxihost.example.com
2025-09-05T15:41:35.478Z In(05) vmx - STATSFILE: StatsFile '/vmfs/volumes/Datastore/VM_name/VM_name.scoreboard' created
2025-09-05T15:41:35.683Z In(05) vmx - Chipset version: 0x13
2025-09-09T20:40:04.173Z In(05) vcpu-0 - Chipset: The guest has requested that the virtual machine be hard reset.
2025-10-15T18:03:38.011Z In(05) vcpu-0 - Chipset: The guest has requested that the virtual machine be powered off.
2025-10-15T18:04:30.813Z In(05) vmx - Hostname=esxihost.example.com
2025-10-15T18:04:30.972Z In(05) vmx - STATSFILE: StatsFile '/vmfs/volumes/Datastore/VM_name/VM_name.scoreboard' created
2025-10-15T18:04:31.055Z In(05) vmx - Chipset version: 0x13
2025-10-16T20:13:10.216Z In(05) vcpu-0 - Chipset: The guest has requested that the virtual machine be hard reset.
- There are no parameters to limit the number of files for the scoreboard. The only advanced setting is to Enable/Disable Scoreboard files.
- If the files are not needed, please disable the scoreboard files which are not necessary using the below operation by seeing the vmx parameter.
vmx.scoreboard.enabled and set it to a value of "false"
However, without any exception, this needs to be done by VM powering Off
https://knowledge.broadcom.com/external/article/376923/scoreboard-is-not-readable-error.html
* scoreboard is not readable error
https://knowledge.broadcom.com/external/article/376923/scoreboard-is-not-readable-error.html