From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LN1xu-00024N-PN for qemu-devel@nongnu.org; Wed, 14 Jan 2009 04:23:10 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LN1xt-000246-2A for qemu-devel@nongnu.org; Wed, 14 Jan 2009 04:23:10 -0500 Received: from [199.232.76.173] (port=57037 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LN1xs-00023y-V7 for qemu-devel@nongnu.org; Wed, 14 Jan 2009 04:23:08 -0500 Received: from mx2.redhat.com ([66.187.237.31]:47066) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LN1xr-0000L6-Ai for qemu-devel@nongnu.org; Wed, 14 Jan 2009 04:23:07 -0500 From: Mark McLoughlin In-Reply-To: <2D739E97-509B-4523-B04B-B18364C152EB@suse.de> References: <496C9813.7000609@suse.de> <496CF614.5000405@codemonkey.ws> <2D739E97-509B-4523-B04B-B18364C152EB@suse.de> Content-Type: text/plain Date: Wed, 14 Jan 2009 09:22:58 +0000 Message-Id: <1231924978.4944.76.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: virtio breakage with 2.6.25 guest kernel Reply-To: Mark McLoughlin , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: "rusty@rustcorp.com.au" , kvm-devel , "qemu-devel@nongnu.org" On Tue, 2009-01-13 at 22:05 +0100, Alexander Graf wrote: > On 13.01.2009, at 21:14, Anthony Liguori 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.