From: Avi Kivity <avi@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] 9p broken?
Date: Mon, 30 Jul 2012 15:35:39 +0300 [thread overview]
Message-ID: <50167F9B.5050003@redhat.com> (raw)
Having an annoying bug on i386 kvm I decided to debug it buy running an
i386 guest on my x86_64 host, use 9p to access a guest image, and run it
using nested kvm.
However, 9p appears to be broken: first, the configure test fails (patch
sent). Second, while mount works, ls on the mount point causes qemu to
crash with
(gdb) bt
#0 error_set (errp=0x7fffe95fb128, fmt=0x5555558d4568 "{ 'class':
'VirtFSFeatureBlocksMigration', 'data': { 'path': %s, 'tag': %s } }") at
/home/tlv/akivity/qemu/error.c:32
#1 0x000055555567cb06 in v9fs_attach (opaque=0x7fffe95e3020) at
/home/tlv/akivity/qemu/hw/9pfs/virtio-9p.c:988
#2 0x000055555561d19f in coroutine_trampoline (i0=1449767888, i1=21845)
at /home/tlv/akivity/qemu/coroutine-ucontext.c:138
#3 0x00007ffff5a93ef0 in ?? () from /lib64/libc.so.6
#4 0x00007fffffffce00 in ?? ()
#5 0x0000000000000000 in ?? (
**errp already points to a VirtFSFeatureBlocksMigration error;
v9fs_attach() has been called a second time (the first time,
understandably, on mount; the second on ls).
Command line:
qemu-system-x86_64 -m 4G -smp 4 -drive
file=/images/Fedora-i386.img,if=virtio,cache=none -cdrom
/images/iso/bfo.iso -device virtio-9p-pci,fsdev=root,mount_tag=root
-fsdev local,id=root,path=/,security_model=passthrough -enable-kvm -net
nic,model=virtio,netdev=net -netdev user,id=net -monitor stdio -cpu host
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2012-07-30 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 12:35 Avi Kivity [this message]
2012-07-30 22:03 ` [Qemu-devel] 9p broken? Richard W.M. Jones
2012-07-31 6:36 ` Aneesh Kumar K.V
2012-07-31 6:51 ` Aneesh Kumar K.V
2012-07-31 12:16 ` Avi Kivity
2012-07-31 13:30 ` Aneesh Kumar K.V
2012-07-31 13:55 ` Avi Kivity
2012-07-31 7:17 ` Aneesh Kumar K.V
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=50167F9B.5050003@redhat.com \
--to=avi@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--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).