From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: Achim Gratz <Stromeko@nexgo.de>
Subject: Re: vmstat yields error 'Unable to create system stat structure' on W11x64
Date: Mon, 16 Jan 2023 11:19:28 +0100 [thread overview]
Message-ID: <Y8UksJ4O2q1+SZn5@calimero.vinschen.de> (raw)
In-Reply-To: <38D69F25-39D2-4A62-B2BD-94055EB2994B@prs.de>
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
next prev parent reply other threads:[~2023-01-16 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 22:04 System Administrator
2023-01-15 22:19 ` Adam Dinwoodie
2023-01-15 23:35 ` System Administrator
2023-01-16 8:45 ` Brian Inglis
2023-01-16 9:34 ` System Administrator
2023-01-16 10:19 ` Corinna Vinschen [this message]
2023-01-16 12:55 ` ASSI
2023-01-16 13:08 ` Corinna Vinschen
2023-01-16 18:47 ` Corinna Vinschen
2023-01-16 19:37 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y8UksJ4O2q1+SZn5@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=Stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).