[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1081416] Re: Qemu 1.2.0 crashes when using tcp serial

From: Ian Wells
Subject: [Qemu-devel] [Bug 1081416] Re: Qemu 1.2.0 crashes when using tcp serial console and GRUB boots
Date: Thu, 18 Jul 2013 13:51:27 -0000

I'm seeing this too.  If someone cares to tell me how I get a core file
from qemu-under-libvirt I will do that and report back on debugging.

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  Qemu 1.2.0 crashes when using tcp serial console and GRUB boots

Status in QEMU:

Bug description:
  When booting OpenWRT Attitude Adjustement ( 
 ) with this command line:
  qemu-system-x86_64 -serial tcp: -hda 

  Qemu crashes as soon as GRUB starts, after network cards start.

  *** buffer overflow detected ***: /usr/bin/qemu-system-x86_64 terminated
  ======= Backtrace: =========

  Here is a GDB backtrace:

  Program received signal SIGABRT, Aborted.
  0x00007ffff452bfa5 in raise () from /usr/lib/libc.so.6
  (gdb) bt
  #0  0x00007ffff452bfa5 in raise () from /usr/lib/libc.so.6
  #1  0x00007ffff452d428 in abort () from /usr/lib/libc.so.6
  #2  0x00007ffff456acfb in __libc_message () from /usr/lib/libc.so.6
  #3  0x00007ffff45f2ad7 in __fortify_fail () from /usr/lib/libc.so.6
  #4  0x00007ffff45f0bb0 in __chk_fail () from /usr/lib/libc.so.6
  #5  0x00007ffff45f2a47 in __fdelt_warn () from /usr/lib/libc.so.6
  #6  0x000000000046a628 in qemu_iohandler_poll (readfds=0xdb7da0 <rfds>, 
      writefds=0xdb7e20 <wfds>, xfds=0x6, address@hidden <xfds>, ret=-1, 
      address@hidden) at iohandler.c:121
  #7  0x00000000004e8a14 in main_loop_wait (nonblocking=<optimized out>)
      at main-loop.c:497
  #8  0x00000000004e802b in main_loop ()
      at /usr/src/aur/qemu/src/qemu-1.2.0/vl.c:1643
  #9  main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>)
      at /usr/src/aur/qemu/src/qemu-1.2.0/vl.c:3755

  Here is a more useless dump...

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]