From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgaJu-0007KE-0a for qemu-devel@nongnu.org; Thu, 27 Aug 2009 04:26:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgaJo-0007HT-3U for qemu-devel@nongnu.org; Thu, 27 Aug 2009 04:26:56 -0400 Received: from [199.232.76.173] (port=38537 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgaJn-0007HB-SN for qemu-devel@nongnu.org; Thu, 27 Aug 2009 04:26:51 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49889) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgaJn-0000mI-7t for qemu-devel@nongnu.org; Thu, 27 Aug 2009 04:26:51 -0400 Message-ID: <4A964345.10008@redhat.com> Date: Thu, 27 Aug 2009 11:26:45 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 2/2] Route IOAPIC interrupts via ISA bus References: <1249836296-13288-1-git-send-email-avi@redhat.com> <1249836296-13288-3-git-send-email-avi@redhat.com> <4A955CB4.4080205@redhat.com> <4A955D6A.9060804@redhat.com> <4A95633E.7060703@redhat.com> <4A961161.5030906@redhat.com> <4A96375D.1070005@redhat.com> <4A963C66.6040300@redhat.com> <4A964013.6000005@redhat.com> In-Reply-To: <4A964013.6000005@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: qemu-devel@nongnu.org On 08/27/2009 11:13 AM, Gerd Hoffmann wrote: > On 08/27/09 09:57, Avi Kivity wrote: >>> What is needed on the guest side? Looks like even 2.6.30 doesn't use >>> MSI for virtio-net ... >> >> virtio msi support was merged in 2.6.31. For e1000, guest support is >> presumably there, just need to wire it into the device. > > lspci shows MSI (not MSI-X) capability for the e1000 in my laptop. It > is not enabled. dmesg has this line though: > > 0000:02:00.0: 0000:02:00.0: Failed to initialize MSI interrupts. > Falling back to legacy interrupts. > > so the driver at least tried to enable MSI ... You probably need chipset support. I recommend drop that laptop and running exclusively in VMs. -- error compiling committee.c: too many arguments to function