[Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

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=0x87709b0e Status in QEMU: Won't Fix Bug descriptio

[Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

Hello, For you information using a Debian 10 distribution resolve the problem. I don't know why but using a CentOS 7 distribution cause this error "qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x82f29b0e" You can close this case if you want, but sti

[Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

. https://bugs.launchpad.net/bugs/1909921 Title: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x87709b0e 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

[Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

berry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x87709b0e 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 wh

[Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

berry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x87709b0e 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 wh

[Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

ch is subscribed to QEMU. https://bugs.launchpad.net/bugs/1909921 Title: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x87709b0e Status in QEMU: New Bug description: Hello, I have a Raspberry Pi 4 with an ESXi hypervisor installed on it (ESXi ARM Ed

[Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

.el7.aarch64 #1 SMP Wed Oct 21 16:25:35 UTC 2020 i686 Binary: 32bit 2021-01-06 22:45:26.227507|WARNING |ServerLibPriv | |The system locale is set to "C" this can cause unexpected behavior. We advice you to repair your locale! qemu:handle_cpu_signal received signal outside vCPU co

[Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

9921 Title: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x87709b0e 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 Dock

[Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

Hello, Can I get any help please? Thank you. Regards, -- 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

[Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

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=0x87709b0e Status in QEMU: New Bug description: Hello, I h

[Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

ainer 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=0x9d5f9b0e qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x82f2

[Bug 1909921] Re: Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

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=0x9d5f9b0e qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xff

[Bug 1909921] [NEW] Raspberry Pi 4 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0xffff87709b0e

o 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=0x82f29b0e (The pc= value is always different, I guess it is randomly generated)

Re: qemu:handle_cpu_signal received signal outside vCPU context

On Thu, 3 Dec 2020 at 10:27, Tj (Elloe Linux) wrote: > > We're seeing this error on Ubuntu 20.04 amd64 host and aarch64 > qemu-aarch64-static chroot when executing 'aptitude': > > qemu:handle_cpu_signal received signal outside vCPU context > qemu:handle_cpu_si

qemu:handle_cpu_signal received signal outside vCPU context

We're seeing this error on Ubuntu 20.04 amd64 host and aarch64 qemu-aarch64-static chroot when executing 'aptitude': qemu:handle_cpu_signal received signal outside vCPU context qemu:handle_cpu_signal received signal outside vCPU context Research led us to an identical issue repo

[Bug 1793539] Re: qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6003ddc5

tle: qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6003ddc5 Status in QEMU: Fix Released Bug description: During the build of gedit for RISC-V this error occurs: $ qemu-riscv64 -E LD_LIBRARY_PATH=gedit/.libs ./gedit/.libs/gedit qemu:handle_cpu_signal received signal outside v

[Bug 1793539] Re: qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6003ddc5

is subscribed to QEMU. https://bugs.launchpad.net/bugs/1793539 Title: qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6003ddc5 Status in QEMU: New Bug description: During the build of gedit for RISC-V this error occurs: $ qemu-riscv64 -E LD_LIBRARY_PATH=gedit/.libs

[Bug 1793539] Re: qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6003ddc5

eived signal outside vCPU context @ pc=0x6003ddc5 Status in QEMU: New Bug description: During the build of gedit for RISC-V this error occurs: $ qemu-riscv64 -E LD_LIBRARY_PATH=gedit/.libs ./gedit/.libs/gedit qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x600

[Qemu-devel] [Bug 1793539] [NEW] qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6003ddc5

Public bug reported: During the build of gedit for RISC-V this error occurs: $ qemu-riscv64 -E LD_LIBRARY_PATH=gedit/.libs ./gedit/.libs/gedit qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6003ddc5 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x69e4

Re: [Qemu-devel] qemu:handle_cpu_signal received signal outside vCPU context

gedit >> --introspect-dump=/tmp/tmp-introspectnj0xla07/functions.txt, >> /tmp/tmp-introspectnj0xla07/dump.xml >> qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6003d7d5 >> qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x60106a16 >> > > Th

Re: [Qemu-devel] qemu:handle_cpu_signal received signal outside vCPU context

On Mär 19 2018, Michael Clark wrote: > I wonder what is the best way for me to reproduce on my side... a tarball > with binaries that I can use to trigger the fault? The easiest way, if you have an OBS account, is to check out the package at

Re: [Qemu-devel] qemu:handle_cpu_signal received signal outside vCPU context

ions.txt, > /tmp/tmp-introspectnj0xla07/dump.xml > qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6003d7d5 > qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x60106a16 > Thanks. I can see this code in accel/tcg/user-exec.c It would be nice if that log message incl

[Qemu-devel] qemu:handle_cpu_signal received signal outside vCPU context

vCPU context @ pc=0x6003d7d5 qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x60106a16 This is qemu as of today with the patches from git://github.com/riscv/riscv-qemu / riscv-all on top. Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9