From: "Philippe Mathieu-Daudé" <1909921@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e
Date: Sun, 03 Jan 2021 19:07:14 -0000 [thread overview]
Message-ID: <160970083537.4456.418376959247113613.launchpad@soybean.canonical.com> (raw)
In-Reply-To: 160969474752.18413.12452840655391947769.malonedeb@gac.canonical.com
** Tags removed: esxi raspberry vmware
** Tags added: linux-user
** Tags added: arm
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1909921
Title:
Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU
context @ pc=0xffff87709b0e
Status in QEMU:
New
Bug description:
Hello,
I have a Raspberry Pi 4 with an ESXi hypervisor installed on it (ESXi ARM Edition).
I created a CentOS 7 VM on it and I'm using a Docker container which is running qemu inside it.
This container is a Debian Bullseye OS and I'm using qemu-i386 to start my application inside it.
The error given by qemu is the following :
qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff9d5f9b0e
qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff82f29b0e
(The pc= value is always different, I guess it is randomly generated).
My qemu version is : qemu-i386 version 5.1.0 (Debian 1:5.1+dfsg-4+b1)
Could you please help me? Why am I facing this error?
Feel free to ask any questions regarding this matter in order to find
a solution to it!
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1909921/+subscriptions
next prev parent reply other threads:[~2021-01-03 19:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 17:25 [Bug 1909921] [NEW] Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e Snoobz
2021-01-03 19:07 ` Philippe Mathieu-Daudé [this message]
2021-01-04 15:30 ` [Bug 1909921] " Alex Bennée
2021-01-04 17:55 ` Snoobz
2021-01-06 21:37 ` Snoobz
2021-01-06 22:22 ` Peter Maydell
2021-01-06 22:50 ` Snoobz
2021-01-06 22:51 ` Snoobz
2021-01-06 22:52 ` Snoobz
2021-01-06 22:53 ` Snoobz
2021-01-08 19:59 ` Snoobz
2021-01-12 19:15 ` Snoobz
2021-05-12 11:31 ` 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=160970083537.4456.418376959247113613.launchpad@soybean.canonical.com \
--to=1909921@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.