Can confirm this bug on fresh Linux Arch and Debian Linux installation.
I need just nothing to reproduce it: Just install fresh arch and do steps
described in comment #1
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.la
Sorry, an error in previous message.
Fixed and detailed diagnostics:
[0... 53248] - working
[53249 ... 61440] - Cannot allocate memory
[61441 ... 65536 and higher] - Operation not permitted
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribe
I mean [0...52348] is working.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-static 5.1 can't run gcc
Status in QEMU:
Fix Released
Status in Juju Charms Collection:
New
Okay, it was found experimentally that the problem is reproduced if
vm.mmap_min_addr is greater than 53249. If from 0 to 53249 - everything
works. What can this be related to?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bu
Sup?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-static 5.1 can't run gcc
Status in QEMU:
Fix Released
Status in Juju Charms Collection:
New
Bug description:
Issue
In my case, sudo does not affect this bug. My output in attachements.
** Attachment added: "sysctl-vm.txt"
https://bugs.launchpad.net/qemu/+bug/1891748/+attachment/5500596/+files/sysctl-vm.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscrib
I think the output of "sysctl vm" could help to identify which parameter
is involved in the problem. You can also compare the output of "sudo
sysctl vm" and "sysctl vm"
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.laun
Okay, what do you think this problem might be related to? I'm glad your
tests are working, but I'm definitely not the only one with this
problem.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
I've been unable to replicate the crash with any of the instructions
here. Certainly all the statically compiled unit tests work and I've
just done a build of QEMU in an emulated Debian Buster (Armel) docker
image.
--
You received this bug notification because you are a member of qemu-
devel-ml,
Anyone?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-static 5.1 can't run gcc
Status in QEMU:
Fix Released
Status in Juju Charms Collection:
New
Bug description:
Is
@aurent-vivier Checked.
This value does not affect the bug, after changing it, I still get an error.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-static 5.1 can't run gcc
** Tags added: arm linux-user tcg
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-static 5.1 can't run gcc
Status in QEMU:
Fix Released
Status in Juju Charms Collection:
Could you check the result of "sysctl vm.mmap_min_addr"
65536 is the value that works for me.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-static 5.1 can't run gcc
Status
It works with sudo, but that can’t be the fix…
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-static 5.1 can't run gcc
Status in QEMU:
Fix Released
Status in Juju Charms C
Heh, even if I omit -static …
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-static 5.1 can't run gcc
Status in QEMU:
Fix Released
Status in Juju Charms Collection:
New
$ qemu-arm --version
qemu-arm version 5.2.0 (Debian 1:5.2+dfsg-6)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
I’m seeing this error on a totally different file:
I’ve made a short test program (hello world-ish) and compiled it with
the OpenWrt toolchain but added -stati
I'm still seeing this with qemu 5.2.0
armv7a-softfp-linux-gnueabi-gcc -O2 -pipe -march=armv7-a -mfpu=vfpv3-d16
-mfloat-abi=softfp -Wl,-O1 -Wl,--as-needed glibc-test.c -o glibc-test
Allocating guest commpage: Operation not permitted
--
You received this bug notification because you are a me
Released with QEMU v5.2.0.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-static 5.1 can't run gcc
Status i
** Also affects: charms
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/1891748
Title:
qemu-arm-static 5.1 can't run gcc
Status in QEMU:
Fix Committed
S
This has been fixed in mainline, probably commit
8ef618859c379fdce81c91bc93e0574e36ea76ff.
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/18917
Plz take a look at this issue please.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-static 5.1 can't run gcc
Status in QEMU:
New
Bug description:
Issue discovered whil
Anyone? Seriously, the problem really exists and we even made a case
that reproduces it. Someone please take a look at this.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-st
Additional info,
error message text ( "Allocating guest commpage" ) found in this commit:
https://fossies.org/diffs/qemu/5.0.0_vs_5.1.0-rc0/linux-user/elfload.c-diff.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs
Steps to reproduce
1. Download and extract attached tarball.
$ make # will build the docker container
$ make run # will enter the container
# once in the container, run
# /qemu-arm-static-50 /bin/bash /runme.sh
** Attachment added: "qemu-1891748-1.tgz"
https://bugs.launchpad.net/qemu/+b
24 matches
Mail list logo