From patchwork Wed Jun 15 08:04:19 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jan Kiszka X-Patchwork-Id: 881322 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by demeter1.kernel.org (8.14.4/8.14.4) with ESMTP id p5F84Wdr014429 for ; Wed, 15 Jun 2011 08:04:32 GMT Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753136Ab1FOIE3 (ORCPT ); Wed, 15 Jun 2011 04:04:29 -0400 Received: from david.siemens.de ([192.35.17.14]:34957 "EHLO david.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752905Ab1FOIE0 (ORCPT ); Wed, 15 Jun 2011 04:04:26 -0400 Received: from mail1.siemens.de (localhost [127.0.0.1]) by david.siemens.de (8.13.6/8.13.6) with ESMTP id p5F84KDm004421; Wed, 15 Jun 2011 10:04:20 +0200 Received: from mchn199C.mchp.siemens.de ([146.254.215.103]) by mail1.siemens.de (8.13.6/8.13.6) with ESMTP id p5F84JeJ023502; Wed, 15 Jun 2011 10:04:19 +0200 Message-ID: <4DF86783.4060608@siemens.com> Date: Wed, 15 Jun 2011 10:04:19 +0200 From: Jan Kiszka User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: Alex Williamson , Flypen CloudMe CC: kvm@vger.kernel.org Subject: Re: Why doesn't Intel e1000 NIC work correctly in Windows XP? References: <1308099263.2515.63.camel@x201> In-Reply-To: <1308099263.2515.63.camel@x201> Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.6 (demeter1.kernel.org [140.211.167.41]); Wed, 15 Jun 2011 08:04:57 +0000 (UTC) On 2011-06-15 02:54, Alex Williamson wrote: > On Tue, 2011-06-14 at 16:11 +0800, Flypen CloudMe wrote: >> Hi, >> >> I use Redhat Enterprise Linux 6, and use the KVM that is released by >> Redhat officially. The kernel version is 2.6.32-71.el6.x86_64. >> >> It seems that the IRQs are conflicted after reboot. The NIC and the >> SCSI controller have the same IRQ number. If I re-install the NIC >> driver, the IRQ number of the NIC will be assigned another value, then >> it can work normally. Do we have a way to let the NIC and the SCSI >> controller have different IRQ number in VM? > > I'll see if I can reproduce and figure anything out. Windows XP isn't a > guest we concentrate on, especially with device assignment. Are you > using an AMD or Intel host system? Does the same thing happen if you > run the XP guest on an IDE controller? It would be helpful to post the > guest configuration, command line used or libvirt xml. Also, you might > try latest upstream qemu-kvm to see if the problem still exists. Maybe tracking of the INTx route across reset fails. Does this help? Jan diff --git a/hw/device-assignment.c b/hw/device-assignment.c index 7eeecad..0693141 100644 --- a/hw/device-assignment.c +++ b/hw/device-assignment.c @@ -1719,6 +1719,8 @@ static void reset_assigned_device(DeviceState *dev) * disconnected from the PCI bus. This avoids further DMA transfers. */ assigned_dev_pci_write_config(pci_dev, PCI_COMMAND, 0, 2); + + assign_irq(adev); } static int assigned_initfn(struct PCIDevice *pci_dev)