From: Ying-Shiuan Pan <yingshiuan.pan@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] virtio-net with virtio-mmio
Date: Wed, 28 Dec 2011 18:16:42 +0800 [thread overview]
Message-ID: <CAA1vHqJpkGju0W2rjMHNPhLxkVHAKa=zcsOakFpGyGezWwp=kQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
Hi, all:
I'm very interested in virtio-mmio Peter Maydell did for QEMU,
(http://lists.nongnu.org/archive/html/qemu-devel/2011-11/msg01870.html)
actually, I've tested the virtio-blk, and it is working.
I applied those patch to QEMU-1.0 and brought the virtio_mmio.c from
Linux-3.2-rc back to Linux-linaro-2.6.38.
I also found a small bug in virito-mmio.c: virtio_mmio_write(),
Peter forgot to break in each case of switch block.
After fixed the small bug, the virtio-balloon works as well.
Then, when I attempted to enable the virtio-net, the initialization part is
fine,
however, the QEMU crashed and printed this message:
"virtio-net header not in first element"
It happens when the front-end virtio-net is invoking virtqueue_kick() at
the end of try_fill_recv().
Then, QEMU gets this message and invokes virtio_net_receive(), then the
error happens.
The parameters I passed to qemu-system-arm is
qemu-system-arm XXXXXXX -netdev type=tap,id=mynet -global
virtio-net-mmio.netdev=mynet
I don't know this is correct or not.
Does anyone have any idea of this problem?
Or give me some directions to solve this bug?
Any comment is welcome. I really appreciate your help!!
----
Best Regards,
Ying-Shiuan Pan
[-- Attachment #2: Type: text/html, Size: 1444 bytes --]
next reply other threads:[~2011-12-28 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 10:16 Ying-Shiuan Pan [this message]
2011-12-30 12:21 ` [Qemu-devel] virtio-net with virtio-mmio Stefan Hajnoczi
2012-01-02 5:19 ` Ying-Shiuan Pan
2012-01-02 17:19 ` Stefan Hajnoczi
2012-01-03 6:37 ` Ying-Shiuan Pan
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='CAA1vHqJpkGju0W2rjMHNPhLxkVHAKa=zcsOakFpGyGezWwp=kQ@mail.gmail.com' \
--to=yingshiuan.pan@gmail.com \
--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).