From: Gordan Bobic <1888303@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1888303] [NEW] Intermittent buggines with user mode emulation of x86-64 on aarch64
Date: Mon, 20 Jul 2020 19:18:37 -0000 [thread overview]
Message-ID: <159527271737.12536.2281351511750409436.malonedeb@gac.canonical.com> (raw)
Public bug reported:
QEMU Version: 5.0.0
./configure --target-list=x86_64-linux-user --enable-user --prefix=/opt/qemu --static
Testing using node_exporter from pmm-client-1.17.4-1.el8.x86_64.rpm
aarch64 system is running CentOS 8 with a mainline 5.4.52 kernel built
for 4KB memory pages.
On aarch64 machine, invoke:
./qemu-x86_64-static /usr/local/percona/pmm-client/node_exporter.x86_64
-web.listen-address=192.168.0.10:42000 -web.auth-file=/usr/local/percona
/pmm-client/pmm.yml -web.ssl-key-file=/usr/local/percona/pmm-
client/server.key -web.ssl-cert-file=/usr/local/percona/pmm-
client/server.crt
-collectors.enabled=diskstats,filefd,filesystem,loadavg,meminfo,netdev,netstat,stat,time,uname,vmstat,meminfo_numa,textfile
Most of the time it will outright segfault within a few seconds,
seemingly when the prometheus server polls for data.
But, about once every 10 times, it will not sefault and will continue
working just fine forever.
The dynamically linked version of qemu (built without --static) always
works without segfaulting, but it just doesn't work, the prometheus
server gets no data from it. Again, once in a while it will work, but
even when it doesn't work it won't segfault.
This vaguely feels like a memory alignment issue somewhere, but my
debug-fu is not quite strong enough to attack the problem.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1888303
Title:
Intermittent buggines with user mode emulation of x86-64 on aarch64
Status in QEMU:
New
Bug description:
QEMU Version: 5.0.0
./configure --target-list=x86_64-linux-user --enable-user --prefix=/opt/qemu --static
Testing using node_exporter from pmm-client-1.17.4-1.el8.x86_64.rpm
aarch64 system is running CentOS 8 with a mainline 5.4.52 kernel built
for 4KB memory pages.
On aarch64 machine, invoke:
./qemu-x86_64-static /usr/local/percona/pmm-
client/node_exporter.x86_64 -web.listen-address=192.168.0.10:42000
-web.auth-file=/usr/local/percona/pmm-client/pmm.yml -web.ssl-key-
file=/usr/local/percona/pmm-client/server.key -web.ssl-cert-
file=/usr/local/percona/pmm-client/server.crt
-collectors.enabled=diskstats,filefd,filesystem,loadavg,meminfo,netdev,netstat,stat,time,uname,vmstat,meminfo_numa,textfile
Most of the time it will outright segfault within a few seconds,
seemingly when the prometheus server polls for data.
But, about once every 10 times, it will not sefault and will continue
working just fine forever.
The dynamically linked version of qemu (built without --static) always
works without segfaulting, but it just doesn't work, the prometheus
server gets no data from it. Again, once in a while it will work, but
even when it doesn't work it won't segfault.
This vaguely feels like a memory alignment issue somewhere, but my
debug-fu is not quite strong enough to attack the problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1888303/+subscriptions
next reply other threads:[~2020-07-20 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 19:18 Gordan Bobic [this message]
2020-07-20 19:25 ` [Bug 1888303] Re: Intermittent buggines with user mode emulation of x86-64 on aarch64 Gordan Bobic
2021-05-07 4:40 ` Thomas Huth
2021-07-07 4:17 ` Launchpad Bug Tracker
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=159527271737.12536.2281351511750409436.malonedeb@gac.canonical.com \
--to=1888303@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.