From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Cc: System Administrator <sysadm@prs.de>
Subject: Re: vmstat yields error 'Unable to create system stat structure' on W11x64
Date: Mon, 16 Jan 2023 01:45:15 -0700 [thread overview]
Message-ID: <5f73c40a-81f1-4e59-bb87-24b56e371eae@Shaw.ca> (raw)
In-Reply-To: <1CCB6238-719D-4C4A-82C5-72A1E1B26A63@prs.de>
On 2023-01-15 16:35, System Administrator via Cygwin wrote:
> On 15. Jan 2023, at 23:19, Adam Dinwoodie <adam@dinwoodie.org> wrote:>> On
Sun, 15 Jan 2023 at 22:05, System Administrator via Cygwin wrote:
>>> 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.
>> Can you provide the cygcheck output, per https://cygwin.com/problems.html?
>> It might be useful to have the cygcheck output from both the Win10 and
>> Win11 VMs to compare, but the Win11 VM where things aren't working is going
>> to be the most useful one there.
>> It might also be useful to know how you're calling vmstat: are you doing it
>> from a Cygwin Bash shell within MinTTY, or from a PowerShell prompt using
>> Windows' console, or something else? And are you running with Administrator
>> privileges?
> please find attached the cygcheck output - apologies for the oversight.
> It does NOT make a difference whether the bash, run from MinTTY (desktop shortcut), is run “As Administrator” or as regular user, the error occurs in both scenarios.
> Running it from PowerShell (both Admin and reg. user) yields the same error.
> P.S. W10 is an older version of Cygwin, but using that one on W11 produces the same erroneous results…
It might also be useful to run vmstat under strace e.g.
$ strace -o vmstat.strace vmstat ...
and attach vmstat.strace as a text attachment to your reply.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-01-16 8:45 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 [this message]
2023-01-16 9:34 ` System Administrator
2023-01-16 10:19 ` Corinna Vinschen
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=5f73c40a-81f1-4e59-bb87-24b56e371eae@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin@cygwin.com \
--cc=sysadm@prs.de \
/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).