On Jan 16 11:19, Corinna Vinschen via Cygwin wrote: > On Jan 15 22:04, System Administrator via Cygwin wrote: > > Hello, > > > > I am trying to migrate my framework to Windows 11 running Cygwin. > > When executing vmstat it returns the following error: > > > > "Unable to create system stat structure” > > [...] > I don't think this has anything to do with Windows10 or 11, but with the > version of procps-ng you're running. > > I tried vmstat from procps-ng-4.0.2-1 on both, W10 and W11, and I got > the above error in both cases. > > I switched back to procps-ng-3.3.17-1 and vmstat worked fine on both, > W10 and W11. > > I ran vmstat from procps-ng-4.0.2-1 under GDB and found that this > vmstat tries to dynamically load libnuma.so or libnuma.1.so, both > of which are naturally not available on Cygwin. So I guess vmstat > from procps-ng-4.x still needs another patch.
While that's obviously wrong, it's not the problem. It turns out that vmstat from procps-ng 4.0.2 stumbles over the fact, that /proc/cpuinfo only prints the following fields if the CPU is a multi core CPU: "physical id" "siblings", "core id" "cpu cores" "apicid" "initial apicid" On Linux the output of those fields only depends on the configuration of the kernel. If it has been built with CONFIG_SMP, these fields are part of the /proc/cpuinfo output. On Cygwin, the output of these fields actually depends on the fact if the HTT CPU flag is set or not. If not, it's not a multi core CPU and the aforementioned fields are omitted. I could reproduce this issue by changing the CPU topology in my QEMU/KVM Windows 10 machine. The default topology was 4 CPUs with 1 core and 1 thread each. I changed that to 2 CPUs with 2 cores and 1 thread each. After restarting the W10 machine, vmstat from procps-ng 4.0.2 started working as desired. So we can fix this issue by tweaking Cygwin instead. I guess this will be fodder for the upcoming 3.4.4 release. I'll also provide a test release in a bit, stay tuned. Achim, I still wonder if vmstat shouldn't also work on Linux if the kernel hasn't been built with CONFIG_SMP. Does the vmstat code fail to take that into account? Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
