Date: Mon, 16 Jan 2023 11:19:28 +0100
To: cygwin@cygwin.com
Subject: Re: vmstat yields error 'Unable to create system stat structure' on
 W11x64
Message-ID: <Y8UksJ4O2q1+SZn5@calimero.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com, Achim Gratz <Stromeko@nexgo.de>
References: <38D69F25-39D2-4A62-B2BD-94055EB2994B@prs.de>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <38D69F25-39D2-4A62-B2BD-94055EB2994B@prs.de>
UI-OutboundReport: notjunk:1;M01:P0:W+3oE2PqJnA=;F9q1vIWAAtKecqfxa4okPCu2fVQ
 zoxoMMy3DWLdYVjYxKuU8QuVm5ENf4YT0t2oqI+lQUnzoZ6qz8Ujya2JhUqLjUquT7vf9DRkN
 PxXk8bdtoRtFDLJRAAcGcldBdaGno/zVYUDeKuDNjUnuX3QYwSR+pHycqkV+nqpH2kUtZDqu5
 abDWrepg0SS4SvJdLZGpMpyuifYi86Ea4NHrowvgCIZLg+x/VIFNmeXGnZ/1LNDVtX176Ya6w
 6JnqqryB3bNYuAohW9LuO+VoIqKTShevQBA+zxNzpZhFY3Xrvd/RxRS2LzS0LuAk/z04Vr7S/
 GxurEeYo+ZVl0mZCMqowiO7LvFfBl2WpXFgZF9xef6nc0HU3/9Ffn1loU4noLVsGmXyKgPhnr
 xh1XGHGFpEt5R6v7EDhkiORai6DEcArQaZFwYVZR6ItvcXFMhD4DfrDqXFU7miTWyQ0wU6I1w
 xUjSLZuMN08sfMAS1ImeWS3QecUtRIJnWIv2Cn3BV4lEndaL2DEnALT0bVr7x+I6atKPaltY1
 NpEq+H5lWXadXpM9wJ/s/w1o8tQpGI+vqpd0UNce/fDrUejMfucNAEgKiQ4kcVQdc+1b8UqM8
 DIjjcz0GTISwfJFlnmeG2xxbnlZGXHyDhvV7ljPI461VE5En5bFL8oGJ5qbofHxekQms0GZ/b
 SfJGKG1nFysqa0oCJM4lngLTPW8M9dT1O+/WPs6eiA==
Precedence: list
From: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>,
        Achim Gratz <Stromeko@nexgo.de>
Content-Type: text/plain; charset="utf-8"
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

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”
> 
> Using the very same packages (install files) on Windows 10, produces the proper vmstat results (i.e. no error).
> I’ve tried W11 pro and Enterprise - same difference (none.) Windows 11 is running in a VMware VM. W11 is the December version wit the latest updates (as of today).
> The working W10 is running on the same physical hardware, using the same version of VMware, also in a VM.
> Cygwin is the latest version 3.4.3, with the latest props-ng package (4.0.2-1)
> 
> Any help (or at least hint) is greatly appreciated.

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.

Achim?


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