From: Thomas Huth <1751674@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1751674] Re: qemu-system-arm segmentation fault using pmemsave on the interrupt controller registers
Date: Sun, 09 May 2021 15:04:25 -0000 [thread overview]
Message-ID: <162057266545.2821.10303428125463218730.malone@wampee.canonical.com> (raw)
In-Reply-To: 151960470707.11772.10064243852456470443.malonedeb@gac.canonical.com
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".
If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:
1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:
https://gitlab.com/qemu-project/qemu/-/issues
and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.
2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" or "Confirmed" within the next 60 days (other-
wise it will get closed as "Expired"). We will then eventually migrate
the ticket automatically to the new system (but you won't be the reporter
of the bug in the new system and thus you won't get notified on changes
anymore).
Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1751674
Title:
qemu-system-arm segmentation fault using pmemsave on the interrupt
controller registers
Status in QEMU:
Incomplete
Bug description:
Qemu segfaults trying to generate a VM memory dump:
$ QEMU_AUDIO_DRV=none qemu-git-src/arm-softmmu/qemu-system-arm -M vexpress-a9 -smp 4 -m 1024 -machine secure=off,dump-guest-core=on -kernel linux-4.9.75/arch/arm/boot/zImage -append "root=/dev/mmcblk0 rw rootfstype=ext4 mem=1024M net.ifnames=0 console=ttyAMA0" -dtb vexpress-v2p-ca9.dtb -sd armv7-hd.qcow2 -netdev tap,ifname=tap_armv7,script=no,downscript=no,id=net0 -device virtio-net-device,mac=00:AA:AD:BB:FF:02,netdev=net0 -monitor stdio -serial vc -loadvm SS0
QEMU 2.11.50 monitor - type 'help' for more information
(qemu) pmemsave 0 0x3FFFFFFF memory.dmp
Segmentation fault (core dumped)
$ git rev-parse HEAD
b384cd95eb9c6f73ad84ed1bb0717a26e29cc78f
It's the second time I try to submit this bug, I think last time it
failed because the attached core dump size (400M compressed). Have a
look if you can get that file, otherwise I will try to update this
ticket once it's created:
(Error ID: OOPS-65553b72bc14be693eb1e37814ff9267)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1751674/+subscriptions
next prev parent reply other threads:[~2021-05-09 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 0:25 [Qemu-devel] [Bug 1751674] [NEW] qemu-system-arm segmentation fault trying to dump VM memory Gustavo Moreira
2018-02-26 0:32 ` [Qemu-devel] [Bug 1751674] " Gustavo Moreira
2018-03-15 14:46 ` Peter Maydell
2018-03-15 14:59 ` Peter Maydell
2018-07-06 13:30 ` Peter Maydell
2021-05-09 15:04 ` Thomas Huth [this message]
2021-05-09 20:47 ` [Bug 1751674] Re: qemu-system-arm segmentation fault using pmemsave on the interrupt controller registers Peter Maydell
2021-05-10 7:43 ` Thomas Huth
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=162057266545.2821.10303428125463218730.malone@wampee.canonical.com \
--to=1751674@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.