From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1285505] Re: [ppa 2.0~git-20140225] SIGABRT with -virtfs
Date: Fri, 28 Feb 2014 18:20:34 -0000 [thread overview]
Message-ID: <20140228182034.12597.71950.malone@wampee.canonical.com> (raw)
In-Reply-To: 20140227060302.21265.95758.malonedeb@chaenomeles.canonical.com
Actually, the interesting bit of the stack trace starts just below where
you cut it off, because object_initialize_with_type() is just asserting
that it wasn't called with a NULL pointer, so what we really want to
know is what the caller was...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1285505
Title:
[ppa 2.0~git-20140225] SIGABRT with -virtfs
Status in QEMU:
New
Status in “qemu” package in Ubuntu:
Triaged
Bug description:
As requested on u-devel@, I tested QEMU
2.0~git-20140225.aa0d1f4-0ubuntu2 from ppa:ubuntu-virt/candidate. This
has a regression with virtfs.
I created a simple cloud-image based VM with autopkgtest:
$ sudo apt-get install autopkgtest
$ adt-buildvm-ubuntu-cloud
This part works fine with the new QEMU (it already boots the cloud-
image in qemu and runs cloud-init). But running it with a shared 9p
directory crashes:
$ mkdir -p /tmp/shared
$ qemu-system-x86_64 -enable-kvm -m 1024 -nographic -virtfs local,id=autopkgtest,path=/tmp/shared,security_model=none,mount_tag=myshare -snapshot adt-trusty-amd64-cloud.img
**
ERROR:/build/buildd/qemu-2.0~git-20140225.aa0d1f4/qom/object.c:331:object_initialize_with_type: assertion failed: (type != NULL)
Abgebrochen (Speicherabzug geschrieben)
It should be easy enough to reproduce and the assertion message
already should be clear, but this is the intersting part of the
(unretraced) stack trace:
#2 0x00007fe3329a9195 in g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x7fe334c5a8e8 "/build/buildd/qemu-2.0~git-20140225.aa0d1f4/qom/object.c", line=line@entry=331, func=func@entry=0x7fe334c5ac40 "object_initialize_with_type", message=message@entry=0x7fe336e06e40 "assertion failed: (type != NULL)") at /build/buildd/glib2.0-2.39.90/./glib/gtestutils.c:2291
lstr = "331\000\377\177\000\000\320ޠF\377\177\000\000\220\026\321\066\343\177\000\000R\252\305\064\343\177\000"
s = 0x7fe336e06e70 "pp\340\066\343\177"
#3 0x00007fe3329a922a in g_assertion_message_expr (domain=0x0, file=0x7fe334c5a8e8 "/build/buildd/qemu-2.0~git-20140225.aa0d1f4/qom/object.c", line=331, func=0x7fe334c5ac40 "object_initialize_with_type", expr=<optimized out>) at /build/buildd/glib2.0-2.39.90/./glib/gtestutils.c:2306
s = 0x7fe336e06e40 "assertion failed: (type != NULL)"
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1285505/+subscriptions
next prev parent reply other threads:[~2014-02-28 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140227060302.21265.95758.malonedeb@chaenomeles.canonical.com>
2014-02-27 17:07 ` [Qemu-devel] [Bug 1285505] Re: [ppa 2.0~git-20140225] SIGABRT with -virtfs Serge Hallyn
2014-02-28 18:09 ` Serge Hallyn
2014-02-28 18:20 ` Peter Maydell [this message]
2014-02-28 19:10 ` Serge Hallyn
2014-02-28 19:17 ` Serge Hallyn
2014-02-28 19:53 ` Serge Hallyn
2014-03-04 23:36 ` Serge Hallyn
2014-03-05 7:21 ` Martin Pitt
2016-10-27 14:34 ` 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=20140228182034.12597.71950.malone@wampee.canonical.com \
--to=peter.maydell@linaro.org \
--cc=1285505@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).