From: Thomas Huth <1713408@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1713408] Re: qemu crashes with "GLib-ERROR **: gmem.c" error when a negative value passed to "maxcpus"
Date: Mon, 28 Aug 2017 11:39:56 -0000 [thread overview]
Message-ID: <150392039662.8320.6319981738598288628.malone@soybean.canonical.com> (raw)
In-Reply-To: 150390171227.19506.41697463404689071.malonedeb@chaenomeles.canonical.com
Please don't add patches to the bug tracker, post them to the qemu-devel
(and qemu-ppc in this case) mailing list instead. You even don't have to
join the mailing lists if you don't like to, posting to them is allowed
for everybody. See https://www.qemu.org/contribute/report-a-bug/ and
http://wiki.qemu.org/Contribute/SubmitAPatch for details. Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1713408
Title:
qemu crashes with "GLib-ERROR **: gmem.c" error when a negative value
passed to "maxcpus"
Status in QEMU:
New
Bug description:
# ppc64-softmmu/qemu-system-ppc64 --nographic -vga none -machine
pseries,accel=kvm,kvm-type=HV -m size=20g -device virtio-blk-
pci,drive=rootdisk -drive file=/home/nasastry/avocado-fvt-wrapper/data
/avocado-
vt/images/pegas-1.0-ppc64le.qcow2,if=none,cache=none,id=rootdisk,format=qcow2
-monitor telnet:127.0.0.1:1234,server,nowait -net nic,model=virtio
-net user -device nec-usb-xhci -smp 8,cores=1,threads=1,maxcpus=-12
(process:12149): GLib-ERROR **: gmem.c:130: failed to allocate
18446744073709550568 bytes
From GDB:
[New Thread 0x3fffb5aceb60 (LWP 12190)]
(process:12184): GLib-ERROR **: gmem.c:130: failed to allocate
18446744073709550568 bytes
Program received signal SIGTRAP, Trace/breakpoint trap.
0x00003fffb75e5408 in raise () from /lib64/libpthread.so.0
Missing separate debuginfos, use: debuginfo-install glib2-2.50.3-3.el7.ppc64le glibc-2.17-196.el7.ppc64le gnutls-3.3.26-9.el7.ppc64le krb5-libs-1.15.1-8.el7.ppc64le libgcc-4.8.5-16.el7.ppc64le libstdc++-4.8.5-16.el7.ppc64le ncurses-libs-5.9-13.20130511.el7.ppc64le nss-3.28.4-8.el7.ppc64le nss-softokn-freebl-3.28.3-6.el7.ppc64le nss-util-3.28.4-3.el7.ppc64le openldap-2.4.44-5.el7.ppc64le openssl-libs-1.0.2k-8.el7.ppc64le p11-kit-0.23.5-3.el7.ppc64le
(gdb) bt
#0 0x00003fffb75e5408 in raise () from /lib64/libpthread.so.0
#1 0x00003fffb796be9c in _g_log_abort () from /lib64/libglib-2.0.so.0
#2 0x00003fffb796d4c4 in g_log_default_handler () from /lib64/libglib-2.0.so.0
#3 0x00003fffb796d86c in g_logv () from /lib64/libglib-2.0.so.0
#4 0x00003fffb796db00 in g_log () from /lib64/libglib-2.0.so.0
#5 0x00003fffb796b694 in g_malloc0 () from /lib64/libglib-2.0.so.0
#6 0x000000001018fa84 in spapr_possible_cpu_arch_ids (machine=0x11165660) at /home/nasastry/upstream/qemu/hw/ppc/spapr.c:3322
#7 0x000000001018b444 in spapr_init_cpus (spapr=0x11165660) at /home/nasastry/upstream/qemu/hw/ppc/spapr.c:2096
#8 0x000000001018bc6c in ppc_spapr_init (machine=0x11165660) at /home/nasastry/upstream/qemu/hw/ppc/spapr.c:2275
#9 0x000000001041ca38 in machine_run_board_init (machine=0x11165660) at hw/core/machine.c:760
#10 0x000000001037723c in main (argc=24, argv=0x3ffffffff108, envp=0x3ffffffff1d0) at vl.c:4633
(gdb) i r
r0 0xfa 250
r1 0x3fffffffe450 70368744170576
r2 0x3fffb7608100 70367525765376
r3 0x0 0
r4 0x2f98 12184
r5 0x5 5
r6 0x0 0
r7 0x3fffa8000020 70367267782688
r8 0x2f98 12184
r9 0x0 0
r10 0x0 0
r11 0x0 0
r12 0x0 0
r13 0x3fffb64fccb0 70367507893424
r14 0x0 0
r15 0x0 0
r16 0x0 0
r17 0x0 0
r18 0x1 1
r19 0x0 0
r20 0x3fffb796d3f0 70367529325552
r21 0x0 0
r22 0x20000000 536870912
r23 0x1 1
r24 0x3fffb7a61498 70367530325144
r25 0x3fffb7a614e8 70367530325224
r26 0x3fffb7a61488 70367530325128
r27 0x3fffa80008c0 70367267784896
r28 0x3fffb79cd2a8 70367529718440
r29 0x3fffb79cd2a8 70367529718440
r30 0xffffffffffffffff 18446744073709551615
r31 0x1 1
pc 0x3fffb75e5408 0x3fffb75e5408 <raise+56>
msr 0x900000000000d033 10376293541461676083
cr 0x42244842 1109674050
lr 0x3fffb796be9c 0x3fffb796be9c <_g_log_abort+60>
ctr 0x0 0
xer 0x0 0
orig_r3 0x2f98 12184
trap 0xc00 3072
Similar error observed on x86_64 and PPC64LE architectures.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1713408/+subscriptions
next prev parent reply other threads:[~2017-08-28 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 6:28 [Qemu-devel] [Bug 1713408] [NEW] qemu crashes with "GLib-ERROR **: gmem.c" error when a negative value passed to "maxcpus" R.Nageswara Sastry
2017-08-28 6:46 ` [Qemu-devel] [Bug 1713408] " R.Nageswara Sastry
2017-08-28 6:56 ` R.Nageswara Sastry
2017-08-28 10:41 ` R.Nageswara Sastry
2017-08-28 11:39 ` Thomas Huth [this message]
2017-08-28 11:40 ` Thomas Huth
2017-08-28 13:35 ` R.Nageswara Sastry
2017-11-03 18:25 ` Peter Maydell
2017-12-15 16:14 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=150392039662.8320.6319981738598288628.malone@soybean.canonical.com \
--to=1713408@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.