Hmm, I'm using qemu-5.1.0 and I'm still seeing this (host is bionic,
container image is focal)
[..]
getsockopt(31, SOL_SOCKET, SO_PEERGROUPS, 0x7ffdbd58941c, [4]) = -1 ERANGE
(Numerical result out of range)
getsockopt(31, SOL_SOCKET, SO_PEERGROUPS, 0x7ffdbd58941c, [4]) = -1 ERANGE
(Numerical
Possibly duplicate of bug #1594394, in which case it would be worth
testing with 5.0.0 or above..
** Bug watch added: github.com/vivier/qemu-m68k/issues #33
https://github.com/vivier/qemu-m68k/issues/33
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Actually more likely https://github.com/vivier/qemu-m68k/issues/33, in
which case it's also fixed..
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1793539
Title:
qemu:handle_cpu_signal received
Possibly
https://github.com/qemu/qemu/commit/6bc024e713fd35eb5fddbe16acd8dc92d27872a9
#diff-6389d258c2de2f974953be12cab45851 ?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1594394
Title:
Using
I think this is probably a duplicate of bug #1594394, in which case it
seems to be fixed in 5.0.0+.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1815911
Title:
aptitude crashes qemu-m68k with
OK, messing around with https://hub.docker.com/r/multiarch/ubuntu-core
for quick testing, it looks like modern versions of qemu do not have
this bug - I used the test case from Bug #1815911 (which I think is
probably a duplicate) and cannot reproduce with:
REPOSITORY
Sorry, heat is definitely getting to me - just realized this is an
upstream bug, not an Ubuntu one! Ubuntu package version is 1:2.11+dfsg-
1ubuntu7.26. At some point I will look at building qemu from source, but
won't be an immediate thing. Apologies for noise .. though if anyone
knows off-hand
(Need a "cd .." after the tar, doh.)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1594394
Title:
Using setreuid / setegid crashes x86_64 user-mode target
Status in QEMU:
New
Bug description:
Sorry, lost your reply in amongst the chaos of my life! OK, quick test
case (type at command line, don't run as script!), host arch is x86-64,
you need qemu-user-static installed..
wget
https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-armhf-root.tar.xz
sudo -s
mkdir armcont
Actually, this is possibly not the same bug. I will add to the list to
investigate further..
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1594394
Title:
Using setreuid / setegid crashes x86_64
Did anything ever happen here? Trying to upgrade Ubuntu ARM container
images using qemu-user on x86-64 from bionic to focal..
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1594394
Title:
Using
11 matches
Mail list logo
