From: Adam Dinwoodie <adam@dinwoodie.org>
To: System Administrator <sysadm@prs.de>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: vmstat yields error 'Unable to create system stat structure' on W11x64
Date: Sun, 15 Jan 2023 22:19:06 +0000 [thread overview]
Message-ID: <CA+kUOamXesqvpkbx4hC1YFb8L35+=sNsomc-rorKREUDBp=q+w@mail.gmail.com> (raw)
In-Reply-To: <38D69F25-39D2-4A62-B2BD-94055EB2994B@prs.de>
On Sun, 15 Jan 2023 at 22:05, 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.
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?
next prev parent reply other threads:[~2023-01-15 22: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 [this message]
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
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='CA+kUOamXesqvpkbx4hC1YFb8L35+=sNsomc-rorKREUDBp=q+w@mail.gmail.com' \
--to=adam@dinwoodie.org \
--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).