From: Mark McLoughlin <markmc@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
kvm-devel <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: virtio breakage with 2.6.25 guest kernel
Date: Wed, 14 Jan 2009 09:22:58 +0000 [thread overview]
Message-ID: <1231924978.4944.76.camel@localhost.localdomain> (raw)
In-Reply-To: <2D739E97-509B-4523-B04B-B18364C152EB@suse.de>
On Tue, 2009-01-13 at 22:05 +0100, Alexander Graf wrote:
> On 13.01.2009, at 21:14, Anthony Liguori <anthony@codemonkey.ws> wrote:
>
> > Alexander Graf wrote:
> >> 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):
> >>
> >
> > There were a couple of old-guest-breaking regressions. I think
> > we've fixed all of them but there could be more. Are you using the
> > latest kvm-userspace?
See:
http://lists.gnu.org/archive/html/qemu-devel/2009-01/msg00574.html
> This one is definitely due to the broken guest kernel. I applied the
> patch mark mentioned to ours and things started working.
>
> So the only way I can think of to 'fix' it is by detecting broken
> guests. We could supply a host mask of 0xffffffff and see if tge guest
> feature mask is tge same. If so, feature masking is probably broken.
Nice idea, but no way of making the guest through feature detection
negotiation, I don't think.
Cheers,
Mark.
next prev parent reply other threads:[~2009-01-14 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 13:33 [Qemu-devel] virtio breakage with 2.6.25 guest kernel Alexander Graf
2009-01-13 13:48 ` 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 [this message]
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=1231924978.4944.76.camel@localhost.localdomain \
--to=markmc@redhat.com \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--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).