Closed m-j-w closed 7 years ago
This is actually wrong. The configuration of vagrant on which pkg listing runs simply uses a hypervisor that tries to hide the real cpu information. Hence this is a non-issue and already mentioned in the form of "don't trust hypervisors".
It appears containers are not hypervisors, but still tamper with cpuid, as observed in #9 on
pkglisting
. That CPU should have AVX2 and different cache sizes, to say the least.This applies at least to Vagrant, possibly also to Docker etc.
Intermediate solution: Update the README.md to give a background and specific limitation note.