Re: [Qemu-devel] [Bug 1285505] Re: [ppa 2.0~git-20140225] SIGABRT with -virtfs

[Serge Hallyn <1285505@bugs.launchpad.net>]

Hm, sadly bisect gives me:

ubuntu@c-trusty-0:~/qemu$ git bisect good
ba1183da9a10b94611cad88c44a5c6df005f9b55 is the first bad commit
commit ba1183da9a10b94611cad88c44a5c6df005f9b55
Author: Fam Zheng <famz@redhat.com>
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 += $(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 <famz@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

:100644 100644 807054b3a1797c911c81c58ae04c15cc599551f6 52b1958b4b43e9e90c68a6339b818f7893ba2551 M      Makefile
:100644 100644 ac1d0e1c285073e1dc881061a3395189074289d0 1914080134d2559c63e76fe0650c9b86e57d3cd8 M      Makefile.objs
:100644 100644 af6ac7eaa19f922cf5d006ee7eebd8ef2dfde3d4 9a6e7dd1b85e75baed2580d51456e614a0ba096f M      Makefile.target
:100755 100755 4648117957465e554bd0005dc51d7e1750b97526 66b1d30c99a83a8856ecfa72bceb55a17928c70c M      configure
:100644 100644 391d6eb8e612e5f7361249fe68040f50eb1c7bcc a95fb76626d5e30b5ac1b4ef5528ba5383f3ccd0 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 “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