From: Alexander Graf <agraf@suse.de>
To: kvm-devel <kvm-devel@lists.sourceforge.net>
Cc: rusty@rustcorp.com.au, qemu-devel@nongnu.org
Subject: [Qemu-devel] virtio breakage with 2.6.25 guest kernel
Date: Tue, 13 Jan 2009 14:33:07 +0100 [thread overview]
Message-ID: <496C9813.7000609@suse.de> (raw)
Hi,
while I don't fully understand the problem, here's what I experience so far:
When using an openSUSE 11.0 kernel (2.6.25) in the guest, virtio on tap
breaks with current KVM git, while it used to work before (haven't
bisected, definitely worked in kvm-78, but is probably due to Anthony's
rewrite). It shows the following message (comes from qemu):
virtio-net header not in first element
This is because qemu expects a message with mergeable rx bufs (12
bytes), but if I see things correctly the old kernel doesn't support
that feature (sends 10 bytes). I put in some debug messages on IO
reads/writes in the qemu virtio handler and got these:
virtio IO read: 0 = 0x100bba3
virtio IO write: 0x4 = 0x100bba3
virtio: setting features 0x100bba3
So I believe the feature masking is somewhat non-functional? Or did I
read the masking code in qemu's virtio-net wrong?
Basically for me, current KVM git broke old guest support, which is a
clear regression and should not happen. Does anybody with more expertise
in virtio want to take on this?
Alex
next reply other threads:[~2009-01-13 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 13:33 Alexander Graf [this message]
2009-01-13 13:48 ` [Qemu-devel] virtio breakage with 2.6.25 guest kernel Mark McLoughlin
2009-01-13 13:59 ` Alexander Graf
2009-01-13 14:00 ` Avi Kivity
2009-01-13 20:14 ` [Qemu-devel] " Anthony Liguori
2009-01-13 21:05 ` Alexander Graf
2009-01-14 9:22 ` Mark McLoughlin
2009-01-15 2:17 ` Rusty Russell
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=496C9813.7000609@suse.de \
--to=agraf@suse.de \
--cc=kvm-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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).