gdb stack dump: Program received signal SIGABRT, Aborted. 0x00007ffff2849f79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/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=sig@entry=6) at ../nptl/sysdeps/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-linux-gnu/libglib-2.0.so.0 #4 0x0000555555783d09 in object_initialize_with_type (data=data@entry=0x7fffe27fd910, size=size@entry=6300032, type=0x0) at qom/object.c:331 #5 0x0000555555783d78 in object_initialize (data=data@entry=0x7fffe27fd910, size=size@entry=6300032, typename=typename@entry=0x555555914f28 "virtio-9p-device") at qom/object.c:350 #6 0x0000555555735153 in virtio_9p_pci_instance_init (obj=0x7fffe27fd010) at hw/virtio/virtio-pci.c:943 #7 0x0000555555783c23 in object_initialize_with_type (data=data@entry=0x7fffe27fd010, size=<optimized out>, type=type@entry=0x5555561c0580) at qom/object.c:342 #8 0x0000555555783dc0 in object_new_with_type (type=0x5555561c0580) at qom/object.c:441 #9 0x0000555555783e55 in object_new (typename=typename@entry=0x5555561c79b0 "virtio-9p-pci") at qom/object.c:451 #10 0x0000555555768d2d in qdev_device_add (opts=0x5555561c7900) at qdev-monitor.c:526 #11 0x00005555557b8289 in device_init_func (opts=<optimized out>, opaque=<optimized out>) at vl.c:2259 #12 0x00005555558da5fb in qemu_opts_foreach (list=<optimized out>, func=0x5555557b8270 <device_init_func>, opaque=0x0, abort_on_failure=<optimized out>) at util/qemu-option.c:1149 #13 0x00005555555e9743 in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) 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 “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