From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: virtio_net sometimes didn't work
Date: Thu, 25 Nov 2010 17:06:34 +0200
Message-ID: <20101125150634.GA17597@redhat.com>
References: <AANLkTimVkOOjooht4Av2H5D_YrbUD+WXnnKXuk25=DoY@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
To: lidong chen <chen.lidong.kernel@gmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:41153 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752494Ab0KYPGr (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 25 Nov 2010 10:06:47 -0500
Content-Disposition: inline
In-Reply-To: <AANLkTimVkOOjooht4Av2H5D_YrbUD+WXnnKXuk25=DoY@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Thu, Nov 25, 2010 at 10:21:24PM +0800, lidong chen wrote:
> [version]
> the host os version is 2.6.32

Which qemu-kvm version?

> the guest os version is 2.6.16
> 
> [dmesg]
> ACPI: (supports S3 S4 S5)
> Freeing unused kernel memory: 200k freed
> input: ImExPS/2 Generic Explorer Mouse as /class/input/input2
> ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
> ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKC] -> GSI 11 (level,
> high) -> IRQ 11
> io address 0001c040ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
> ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LNKD] -> GSI 10 (level,
> high) -> IRQ 10
> io address 0001c060ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
> ACPI: PCI Interrupt 0000:00:05.0[A] -> Link [LNKA] -> GSI 10 (level,
> high) -> IRQ 10
> io address 0001c080ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
> ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKB] -> GSI 11 (level,
> high) -> IRQ 11
> io address 0001c0a0<6>ACPI: PCI Interrupt 0000:00:07.0[A] -> Link
> [LNKC] -> GSI 11 (level, high) -> IRQ 11
> io address 0001c0c0<6>ACPI: PCI Interrupt 0000:00:08.0[A] -> Link
> [LNKD] -> GSI 10 (level, high) -> IRQ 10
> io address 0001c0e0
> irq 11: nobody cared (try booting with the "irqpoll" option)
>  [<c01457b0>] __report_bad_irq+0x2b/0x69
>  [<c0145979>] note_interrupt+0x18b/0x1b2
>  [<c01452a9>] handle_IRQ_event+0x26/0x51
>  [<c014537f>] __do_IRQ+0xab/0xdc
>  [<c0106445>] do_IRQ+0x46/0x53
>  [<c0104e8a>] common_interrupt+0x1a/0x20
>  [<c01276f2>] __do_softirq+0x4f/0xc2
>  [<c0127793>] do_softirq+0x2e/0x32
>  [<c0104f3c>] apic_timer_interrupt+0x1c/0x30
>  [<c0102d55>] default_idle+0x2e/0x5c
>  [<c0102e14>] cpu_idle+0x91/0xad
>  [<c03946e5>] start_kernel+0x34c/0x353
> handlers:
> [<f88252ee>] (vp_interrupt+0x0/0x3e [virtio_pci])
> Disabling IRQ #11

Does this message appear on boot, or after some stress?
Does cherry-picking 3fff0179e33cd7d0a688dab65700c46ad089e934 help?
Happens with a newer kernel as guest?
What does info irqs show in qemu?


-- 
MST