From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: vhost-net patches Date: Thu, 22 Oct 2009 19:36:10 +0200 Message-ID: <20091022173609.GA10686@redhat.com> References: <20091020171832.GE13378@redhat.com> <20091020173259.GA14639@redhat.com> <20091021201923.GA25520@redhat.com> <20091022123456.GA6682@redhat.com> <20091022131332.GB6961@redhat.com> <1256232224.6601.17.camel@localhost.localdomain> <1256232775.6601.24.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Shirley Ma , David Stevens , kvm@vger.kernel.org, sri@linux.vnet.ibm.com, mashirle@linux.vnet.ibm.com To: Shirley Ma Return-path: Received: from mx1.redhat.com ([209.132.183.28]:47705 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752615AbZJVRic (ORCPT ); Thu, 22 Oct 2009 13:38:32 -0400 Content-Disposition: inline In-Reply-To: <1256232775.6601.24.camel@localhost.localdomain> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Oct 22, 2009 at 10:32:55AM -0700, Shirley Ma wrote: > On Thu, 2009-10-22 at 10:23 -0700, Shirley Ma wrote: > > Yes, agreed. One observation is when I enable PCI MSI in guest kernel, > > I > > found that even without vhost supportin host kernel the network > > doesn't > > work either. So I think this is nothing related to vhost. I need to > > find > > why PCI MSI doesn't work for me. > > Let me clarify this, here is the table: > > 1. upstream qemu + guest kernel MSI support --- doesn't work > 2. upstream qemu + guest kernel no MSI support --- work > 3. mst qemu git tree + guest kernel MSI support - vhost --- work > 4. mst qemu git tree + guest kernel MSI support + vhost -- doesn't work Upstream is Avi's qemu-kvm.git? So, for a moment taking vhost out of the equation, it seems that MSI was broken in Avi's tree again, after I forked my tree? > > I hope it's clear. > > thanks > Shirley