Rather than backporting slirp fixes from 2.7.0 to 2.5.0, how about qemu
2.7 or 2.8 in backports?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226
Title:
segfault in qemu-system-x86_64
To manag
[Expired for qemu (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226
Tit
I have been working with the qemu devs, was able to reproduce the slirp
networking crashes under valgrind, and they provided a fix:
http://lists.nongnu.org/archive/html/qemu-devel/2016-11/msg02411.html
The fix has also been merged upstream:
commit ea64d5f08817b5e79e17135dce516c7583107f91
Author:
Sorry about this - the repo was open at the time I posted but is
currently closed for layer 9 reasons. I am trying to get permission to
release this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16302
Hi Brian,
thanks for your persistence, reproductions and debugging a lot!
I was trying to follow your reproduction steps, but your vtp repo is
behind a user authentication that is neither the "normal" gitlab nor
does it show any option to register a new user.
Can you share that at some place we c
FYI, update:
- I have upgraded my Mac Mini to 16.04 (plus qemu 2.7.0 from source)
- I have completely replaced the RAM in my Mac Mini
- I have replicated on someone else's Mac Mini with 16.04
I can still replicate the new segfault/libc problems, so I'm sure that
it's not a hardware issue.
The ne
I found that when I have
[ "-smp", "8,sockets=1,cores=4,threads=2" ],
in packer_files/vtp.json, the build completes successfully on my 14.04
Mac Mini with qemu 2.7.0. It worked several times flawlessly.
But if I remove that line (so that only one CPU is emulated by KVM) then
I get errors
> how can we reproduce this? Can you give a precise set of steps to
download/build an image and run qemu with it?
(1) The first issue - segfault in slirp/tcp_output.c - which is also
this one:
https://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg03636.html
You can reproduce using the proj
Hi,
how can we reproduce this? Can you give a precise set of steps to
download/build an image and run qemu with it?
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
I have now tried this on someone else's Mac Mini, this one running
16.04.1.
With the stock qemu (1:2.5+dfsg-5ubuntu10.5), it crashes in apparently
the same way as mine was doing originally:
Oct 5 14:59:49 s1 kernel: [3982196.302758] qemu-system-x86[20590]:
segfault at 55fc165caa20 ip 55fd12d
Hmm, a different malloc-type error on next run:
Program received signal SIGABRT, Aborted.
0x7f7b20acbc37 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x7f7b20acbc37 in __
For comparison I built qemu-2.5.1.1 from the release tarball at
http://wiki.qemu.org/Download, using the same configure options. (I
picked that one as being closest to what's in xenial)
And it crashes in exactly the same place:
Program received signal SIGSEGV, Segmentation fault.
tcp_output (tp=t
It depends on a ton of libraries (literally):
$ ldd /usr/bin/qemu-system-x86_64 | wc -l
100
But using the dev packages I already had around, plus libfdt-dev which
it insisted on, I have done the following:
apt-get source qemu-system-x86
cd qemu-2.0.0+dfsg
./configure --disable-strip --target-lis
Could you build qemu from upstream git and run that under gdb to
reproduce and get a full stack trace?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226
Title:
segfault in qemu-system-x86_64
To
I installed some more *-dbg and *-devel packages (including
libstdc++6-4.8-dbg), and now the backtrace is marginally more helpful -
although possibly this is a different trace?
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f95f3fff700 (LWP 10149)]
__memcpy_sse2_unal
Attaching gdb to a running process gives the same result as I got from
the core dump.
(gdb) cont
Continuing.
[Thread 0x7f2877cfe700 (LWP 10805) exited]
[Thread 0x7f2876cfc700 (LWP 10816) exited]
[Thread 0x7f28774fd700 (LWP 10815) exited]
[Thread 0x7f2c015ff700 (LWP 10735) exited]
[Thread 0x7f2c098
16 matches
Mail list logo
