System log - pvestatd CPU flag detection failed, will try again after delay

[rrawstron]

The system log shows recurring entries for pvestatd[pid] CPU flag detection failed, will try again after delay.
See below.

This doesn't appear to be causing problems.
Proxmox, the two Debian containers and one Windows 10 VM are working as expected.

However why does this occur?
Is this a bug?
Or simply due to using an older CPU? See below.
Can Proxmox be configured so these log entries don't occur? i.e. for cleaner logs.

A thread was raised last year for a similar issue on similar hardware however no info/solution was posted.
https://forum.proxmox.com/threads/cpu-flag-detection-failed-will-try-again-after-delay.131022/

Sep 05 17:20:58 pve pvestatd[1083]: warning: failed querying supported tcg flags: QEMU flag querying VM exited with code 127 at /usr/share/perl5/PVE/QemuServer.pm line 3385.
Sep 05 17:20:58 pve pvestatd[1083]: warning: failed querying supported kvm flags: QEMU flag querying VM exited with code 127 at /usr/share/perl5/PVE/QemuServer.pm line 3385.
Sep 05 17:20:58 pve pvestatd[1083]: CPU flag detection failed, will try again after delay
Sep 05 17:22:58 pve pvestatd[1083]: warning: failed querying supported tcg flags: QEMU flag querying VM exited with code 127 at /usr/share/perl5/PVE/QemuServer.pm line 3385.
Sep 05 17:22:58 pve pvestatd[1083]: warning: failed querying supported kvm flags: QEMU flag querying VM exited with code 127 at /usr/share/perl5/PVE/QemuServer.pm line 3385.
Sep 05 17:22:58 pve pvestatd[1083]: CPU flag detection failed, will try again after delay

Environment:

Hardware	HP Proliant Microserver G8 https://support.hpe.com/connect/s/product?language=en_US&kmpmoid=5379860&tab=driversAndSoftware
CPU	Intel(R) Xeon(R) CPU E3-1265L V2 @ 2.50GHz Supports VT-x https://ark.intel.com/content/www/u...-processor-e3-1265l-v2-8m-cache-2-50-ghz.html
Proxmox	8.2.4 Installed from proxmox-ve_8.2-1.iso All updates applied
Kernel	Linux pve 6.8.12-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-1 (2024-08-05T16:17Z) x86_64 GNU/Linux

lscpu output

Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          36 bits physical, 48 bits virtual
  Byte Order:             Little Endian
CPU(s):                   8
  On-line CPU(s) list:    0-7
Vendor ID:                GenuineIntel
  BIOS Vendor ID:         Intel
  Model name:             Intel(R) Xeon(R) CPU E3-1265L V2 @ 2.50GHz
    BIOS Model name:       Intel(R) Xeon(R) CPU E3-1265L V2 @ 2.50GHz       CPU @ 2.5GHz
    BIOS CPU family:      179
    CPU family:           6
    Model:                58
    Thread(s) per core:   2
    Core(s) per socket:   4
    Socket(s):            1
    Stepping:             9
    CPU(s) scaling MHz:   93%
    CPU max MHz:          3500.0000
    CPU min MHz:          1600.0000
    BogoMIPS:             4988.83
    Flags:                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good
                           nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx
                          f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts vnmi md_clear flush_l1d
Virtualization features: 
  Virtualization:         VT-x
Caches (sum of all):     
  L1d:                    128 KiB (4 instances)
  L1i:                    128 KiB (4 instances)
  L2:                     1 MiB (4 instances)
  L3:                     8 MiB (1 instance)
NUMA:                    
  NUMA node(s):           1
  NUMA node0 CPU(s):      0-7
Vulnerabilities:         
  Gather data sampling:   Not affected
  Itlb multihit:          KVM: Mitigation: VMX disabled
  L1tf:                   Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
  Mds:                    Mitigation; Clear CPU buffers; SMT vulnerable
  Meltdown:               Mitigation; PTI
  Mmio stale data:        Unknown: No mitigations
  Reg file data sampling: Not affected
  Retbleed:               Not affected
  Spec rstack overflow:   Not affected
  Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:             Mitigation; Retpolines; IBPB conditional; IBRS_FW; STIBP conditional; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
  Srbds:                  Vulnerable: No microcode
  Tsx async abort:        Not affected