OK, I finally got access to the VMs and was able to check the VMWare version there:
$ vmware-toolbox-cmd -v 10.3.0.5330 (build-8931395)
So it's pre-VMWare 11. And I double checked and confirmed that we can't reproduce the problem reported here indeed:
# apt policy dmidecode dmidecode: Installed: 3.1-1 ... # cat /sys/class/dmi/id/product_uuid 42187693-2BD2-5AF3-BDA4-AAF4E13CA373 # cat /sys/class/dmi/id/product_uuid 42187693-2BD2-5AF3-BDA4-AAF4E13CA373
As I said above, the patch pointed at [1] is already present on 3.1-1 (in fact, it's been available since version 2.10), so there's something else going on here.
Were you able to confirm that dmidecode 3.2 fixes the issue for you?
Cheers.
[1]: https://github.com/mirror/dmidecode/commit/7a9fc6d3cba86ec9c517b8ec314e099c5cb433b9
OK, I finally got access to the VMs and was able to check the VMWare version there:
$ vmware-toolbox-cmd -v
10.3.0.5330 (build-8931395)
So it's pre-VMWare 11. And I double checked and confirmed that we can't reproduce the problem reported here indeed:
# apt policy dmidecode dmi/id/ product_ uuid 2BD2-5AF3- BDA4-AAF4E13CA3 73 dmi/id/ product_ uuid 2BD2-5AF3- BDA4-AAF4E13CA3 73
dmidecode:
Installed: 3.1-1
...
# cat /sys/class/
42187693-
# cat /sys/class/
42187693-
As I said above, the patch pointed at [1] is already present on 3.1-1 (in fact, it's been available since version 2.10), so there's something else going on here.
Were you able to confirm that dmidecode 3.2 fixes the issue for you?
Cheers.
[1]: https:/ /github. com/mirror/ dmidecode/ commit/ 7a9fc6d3cba86ec 9c517b8ec314e09 9c5cb433b9