From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60851) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WJSzY-0006Rc-9c for qemu-devel@nongnu.org; Fri, 28 Feb 2014 14:21:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WJSzQ-0004IQ-Iq for qemu-devel@nongnu.org; Fri, 28 Feb 2014 14:21:04 -0500 Received: from indium.canonical.com ([91.189.90.7]:37755) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WJSzQ-0004IE-A0 for qemu-devel@nongnu.org; Fri, 28 Feb 2014 14:20:56 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1WJSzM-0004q5-U7 for ; Fri, 28 Feb 2014 19:20:53 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id BC07D2EA084 for ; Fri, 28 Feb 2014 19:20:45 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Fri, 28 Feb 2014 19:10:59 -0000 From: Serge Hallyn <1285505@bugs.launchpad.net> Sender: bounces@canonical.com References: <20140227060302.21265.95758.malonedeb@chaenomeles.canonical.com> <20140228182034.12597.71950.malone@wampee.canonical.com> Message-Id: <20140228191059.GA3611@sergelap> Errors-To: bounces@canonical.com Subject: Re: [Qemu-devel] [Bug 1285505] Re: [ppa 2.0~git-20140225] SIGABRT with -virtfs Reply-To: Bug 1285505 <1285505@bugs.launchpad.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hm, sadly bisect gives me: ubuntu@c-trusty-0:~/qemu$ git bisect good ba1183da9a10b94611cad88c44a5c6df005f9b55 is the first bad commit commit ba1183da9a10b94611cad88c44a5c6df005f9b55 Author: Fam Zheng Date: Mon Feb 10 14:48:52 2014 +0800 rules.mak: fix $(obj) to a real relative path = Makefile.target includes rule.mak and unnested common-obj-y, then prefix them with '../', this will ignore object specific QEMU_CFLAGS in subdir Makefile.objs: = $(obj)/curl.o: QEMU_CFLAGS +=3D $(CURL_CFLAGS) = Because $(obj) here is './block', instead of '../block'. This doesn't hurt compiling because we basically build all .o from top Makefile, before entering Makefile.target, but it will affact arriving per-object libs support. = The starting point of $(obj) is passed in as argument of unnest-vars, as well as nested variables, so that different Makefiles can pass in a right value. = Signed-off-by: Fam Zheng Signed-off-by: Paolo Bonzini :100644 100644 807054b3a1797c911c81c58ae04c15cc599551f6 52b1958b4b43e9e90c6= 8a6339b818f7893ba2551 M Makefile :100644 100644 ac1d0e1c285073e1dc881061a3395189074289d0 1914080134d2559c63e= 76fe0650c9b86e57d3cd8 M Makefile.objs :100644 100644 af6ac7eaa19f922cf5d006ee7eebd8ef2dfde3d4 9a6e7dd1b85e75baed2= 580d51456e614a0ba096f M Makefile.target :100755 100755 4648117957465e554bd0005dc51d7e1750b97526 66b1d30c99a83a8856e= cfa72bceb55a17928c70c M configure :100644 100644 391d6eb8e612e5f7361249fe68040f50eb1c7bcc a95fb76626d5e30b5ac= 1b4ef5528ba5383f3ccd0 M rules.mak -- = 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 =E2=80=9Cqemu=E2=80=9D 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: =C2=A0=C2=A0$ sudo apt-get install autopkgtest =C2=A0=C2=A0$ 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: =C2=A0=C2=A0$ mkdir -p /tmp/shared =C2=A0=C2=A0$ qemu-system-x86_64 -enable-kvm -m 1024 -nographic -virtfs l= ocal,id=3Dautopkgtest,path=3D/tmp/shared,security_model=3Dnone,mount_tag=3D= 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 !=3D 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: =C2=A0#2 0x00007fe3329a9195 in g_assertion_message (domain=3Ddomain@entr= y=3D0x0, file=3Dfile@entry=3D0x7fe334c5a8e8 "/build/buildd/qemu-2.0~git-201= 40225.aa0d1f4/qom/object.c", line=3Dline@entry=3D331, func=3Dfunc@entry=3D0= x7fe334c5ac40 "object_initialize_with_type", message=3Dmessage@entry=3D0x7f= e336e06e40 "assertion failed: (type !=3D NULL)") at /build/buildd/glib2.0-2= .39.90/./glib/gtestutils.c:2291 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0lstr =3D "331\000\3= 77\177\000\000\320=DE=A0F\377\177\000\000\220\026\321\066\343\177\000\000R\= 252\305\064\343\177\000" =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0s =3D 0x7fe336e06e7= 0 "pp\340\066\343\177" =C2=A0#3 0x00007fe3329a922a in g_assertion_message_expr (domain=3D0x0, f= ile=3D0x7fe334c5a8e8 "/build/buildd/qemu-2.0~git-20140225.aa0d1f4/qom/objec= t.c", line=3D331, func=3D0x7fe334c5ac40 "object_initialize_with_type", expr= =3D) at /build/buildd/glib2.0-2.39.90/./glib/gtestutils.c:23= 06 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0s =3D 0x7fe336e06e4= 0 "assertion failed: (type !=3D NULL)" To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1285505/+subscriptions