[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1405385
Title:
QEMU
Looking through old bug tickets... Bram, can you still reproduce this
issue with the latest version of QEMU? Or could we close this ticket
nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
On Fri, Jan 09, 2015 at 07:30:05AM -, Bram Klein Gunnewiek wrote:
I'm not sure if there is more information required from my side? I can
still reproduce this and have no clue where to look for more
information.
I cannot reproduce a crash from your command-line with qemu.git/master
I'm not sure if there is more information required from my side? I can
still reproduce this and have no clue where to look for more
information.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1405385
I have a hard time getting a full backtrace. I recompiled qemu with
--enable-debug. Running QEMU with -s -S and then using GDB with debug
using: attach remote localhost:1234 works but when QEMU has crashed the
command bt full always gives back:
(gdb) bt full
No stack.
I then ran QEMU directly
On 29 December 2014 at 08:29, Bram Klein Gunnewiek
1405...@bugs.launchpad.net wrote:
Right before QEMU crashes I get this error in gdb:
Program received signal SIGUSR1, User defined signal 1.
SIGUSR1 is used internally by QEMU. You can tell gdb not to
bother you about it:
handle SIGUSR1 pass
I can't reproduce this, no matter how hard I try. Tried 4 virtio devices
and 4 e1000 devices (8 network devices in total). Tried 2.1 and 2.2 and
current git. It all Just Works (tm). What I'm doing wrong? :)
--
You received this bug notification because you are a member of qemu-
devel-ml,
I think your just not trying hard enough ;-)
I have reproduced this on four different (bare metal) machines. I used
the default ubuntu QEMU (2.0.0) and the latest GIT version. All machines
where running ubuntu 14.04. I also tried to reproduce it on a virtualbox
VM and I could only get it to crash
What does qemu say when aborting?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1405385
Title:
QEMU crashes when virtio network cards are used together with e1000
network cards
Status in QEMU:
Hm. I guess it says nothing, as else some write(2) should be seen by
strace. So it is like abort() not assert(). And we have about 800
abort() calls in the code. Oh well.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Indeed, it does not say anything, it simply crashes. Besides the strace
log I created I can't find any other usefull information in other
logfiles.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
a backtrace from a coredump or gdb would be better; it'll tell us the line the
abort is on and the state at that point.
Run it under gdb and do
bt full
and paste the result.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
12 matches
Mail list logo
