From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33495) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WJT4F-0008Az-9D for qemu-devel@nongnu.org; Fri, 28 Feb 2014 14:26:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WJT49-0005xd-8H for qemu-devel@nongnu.org; Fri, 28 Feb 2014 14:25:55 -0500 Received: from indium.canonical.com ([91.189.90.7]:39197) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WJT49-0005xX-0Y for qemu-devel@nongnu.org; Fri, 28 Feb 2014 14:25:49 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1WJT48-0006bJ-7l for ; Fri, 28 Feb 2014 19:25:48 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 3296D2E80C3 for ; Fri, 28 Feb 2014 19:25:48 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Fri, 28 Feb 2014 19:17:28 -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: <20140228191728.GA3731@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 gdb stack dump: Program received signal SIGABRT, Aborted. 0x00007ffff2849f79 in __GI_raise (sig=3Dsig@entry=3D6) at ../nptl/sysdeps/u= nix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) where #0 0x00007ffff2849f79 in __GI_raise (sig=3Dsig@entry=3D6) at ../nptl/sysde= ps/unix/sysv/linux/raise.c:56 #1 0x00007ffff284d388 in __GI_abort () at abort.c:89 #2 0x00007ffff793c195 in g_assertion_message () from /lib/x86_64-linux-gnu= /libglib-2.0.so.0 #3 0x00007ffff793c22a in g_assertion_message_expr () from /lib/x86_64-linu= x-gnu/libglib-2.0.so.0 #4 0x0000555555783d09 in object_initialize_with_type (data=3Ddata@entry=3D= 0x7fffe27fd910, = size=3Dsize@entry=3D6300032, type=3D0x0) at qom/object.c:331 #5 0x0000555555783d78 in object_initialize (data=3Ddata@entry=3D0x7fffe27f= d910, size=3Dsize@entry=3D6300032, = typename=3Dtypename@entry=3D0x555555914f28 "virtio-9p-device") at qom/o= bject.c:350 #6 0x0000555555735153 in virtio_9p_pci_instance_init (obj=3D0x7fffe27fd010= ) at hw/virtio/virtio-pci.c:943 #7 0x0000555555783c23 in object_initialize_with_type (data=3Ddata@entry=3D= 0x7fffe27fd010, = size=3D, type=3Dtype@entry=3D0x5555561c0580) at qom/obje= ct.c:342 #8 0x0000555555783dc0 in object_new_with_type (type=3D0x5555561c0580) at q= om/object.c:441 #9 0x0000555555783e55 in object_new (typename=3Dtypename@entry=3D0x5555561= c79b0 "virtio-9p-pci") at qom/object.c:451 #10 0x0000555555768d2d in qdev_device_add (opts=3D0x5555561c7900) at qdev-m= onitor.c:526 #11 0x00005555557b8289 in device_init_func (opts=3D, opaque= =3D) at vl.c:2259 #12 0x00005555558da5fb in qemu_opts_foreach (list=3D, = func=3D0x5555557b8270 , opaque=3D0x0, abort_on_failur= e=3D) at util/qemu-option.c:1149 #13 0x00005555555e9743 in main (argc=3D, argv=3D, envp=3D) at vl.c:4249 -- = 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