On Wed, 2014-01-15 at 16:59 +0800, 李义 wrote:
> >Which OS is this, exactly?
> >Does this reproduce with a newer guest?
>
> the guest kernel (2.6.32.43) is come from the mainline of kernel.org.
> this issue just happened once at my guest kernel (2.6.32.43).
What are the options used to start the VM, ex. ps aux | grep qemu
What are the kernel options for the guest? Are you using anything like
pci=nomsi to disable MSI support on the virtio devices? Thanks,
Alex
> >What uses irq 11? Could you check with lspci before you try to shutdown?
>
> # lspci
> 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
> 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
> 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
> 00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB
> [Natoma/Triton II] (rev 01)
> 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
> 00:02.0 VGA compatible controller: Cirrus Logic GD 5446
> 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
> 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device
> 00:05.0 SCSI storage controller: Red Hat, Inc Virtio block device
> 00:06.0 SCSI storage controller: Red Hat, Inc Virtio block device
> 00:07.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon
>
> # lspci -vv
> 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
> Subsystem: Red Hat, Inc Qemu virtual machine
> Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>
> 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
> Subsystem: Red Hat, Inc Qemu virtual machine
> Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>
> 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE
> [Natoma/Triton II] (prog-if 80 [Master])
> Subsystem: Red Hat, Inc Qemu virtual machine
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
> Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
> Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
> Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
> Region 4: I/O ports at c100 [size=16]
> Kernel driver in use: ata_piix
>
> 00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB
> [Natoma/Triton II] (rev 01) (prog-if 00 [UHCI])
> Subsystem: Red Hat, Inc Qemu virtual machine
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin D routed to IRQ 11
> Region 4: I/O ports at c080 [size=32]
>
> 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
> Subsystem: Red Hat, Inc Qemu virtual machine
> Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Interrupt: pin A routed to IRQ 9
>
> 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00
> [VGA controller])
> Subsystem: Red Hat, Inc Device 1100
> Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Region 0: Memory at fc000000 (32-bit, prefetchable) [size=32M]
> Region 1: Memory at febf0000 (32-bit, non-prefetchable) [size=4K]
> Expansion ROM at febe0000 [disabled] [size=64K]
>
> 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
> Subsystem: Red Hat, Inc Device 0001
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 11
> Region 0: I/O ports at c0a0 [size=32]
> Region 1: Memory at febf1000 (32-bit, non-prefetchable) [size=4K]
> Expansion ROM at feba0000 [disabled] [size=128K]
> Capabilities: [40] MSI-X: Enable+ Count=3 Masked-
> Vector table: BAR=1 offset=00000000
> PBA: BAR=1 offset=00000800
> Kernel driver in use: virtio-pci
>
> 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device
> Subsystem: Red Hat, Inc Device 0001
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 10
> Region 0: I/O ports at c0c0 [size=32]
> Region 1: Memory at febf2000 (32-bit, non-prefetchable) [size=4K]
> Expansion ROM at febc0000 [disabled] [size=128K]
> Capabilities: [40] MSI-X: Enable+ Count=3 Masked-
> Vector table: BAR=1 offset=00000000
> PBA: BAR=1 offset=00000800
> Kernel driver in use: virtio-pci
>
> 00:05.0 SCSI storage controller: Red Hat, Inc Virtio block device
> Subsystem: Red Hat, Inc Device 0002
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 10
> Region 0: I/O ports at c000 [size=64]
> Region 1: Memory at febf3000 (32-bit, non-prefetchable) [size=4K]
> Capabilities: [40] MSI-X: Enable+ Count=2 Masked-
> Vector table: BAR=1 offset=00000000
> PBA: BAR=1 offset=00000800
> Kernel driver in use: virtio-pci
>
> 00:06.0 SCSI storage controller: Red Hat, Inc Virtio block device
> Subsystem: Red Hat, Inc Device 0002
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 11
> Region 0: I/O ports at c040 [size=64]
> Region 1: Memory at febf4000 (32-bit, non-prefetchable) [size=4K]
> Capabilities: [40] MSI-X: Enable+ Count=2 Masked-
> Vector table: BAR=1 offset=00000000
> PBA: BAR=1 offset=00000800
> Kernel driver in use: virtio-pci
>
> 00:07.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon
> Subsystem: Red Hat, Inc Device 0005
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 11
> Region 0: I/O ports at c0e0 [size=32]
> Kernel driver in use: virtio-pc
>
> 2014/1/15, Michael S. Tsirkin <mst@xxxxxxxxxx>:
> > On Wed, Jan 15, 2014 at 02:48:35PM +0800, 李义 wrote:
> >> Hi ALL,
> >>
> >> i have meet kvm guest os issue at redhat7beta.
> >>
> >> Host os:
> >> iredhat7 Beta
> >> #virsh version
> >> Compiled against library: libvirt 1.1.1
> >> Using library: libvirt 1.1.1
> >> Using API: QEMU 1.1.1
> >> Running hypervisor: QEMU 1.5.3
> >>
> >> guest os:
> >> 2.6.32.43 x86-64
> >
> > Which OS is this, exactly?
> > Does this reproduce with a newer guest?
> >
> >> Problem:
> >> reboot at the guest os, the guest os will hang.(i have not find the
> >> reproduce method)
> >>
> >> pls: the below is the crash info.
> >>
> >> [ 3.446282] Adding 2104504k swap on /dev/vda2. Priority:-1
> >> extents:1 across:2104504k
> >> [ 63.862133] md: stopping all md devices.
> >> [ 64.960702] ACPI: Preparing to enter system sleep state S5
> >> [ 64.961280] Disabling non-boot CPUs ...
> >> [ 66.370651] irq 11: nobody cared (try booting with the "irqpoll"
> >> option)
> >
> > What uses irq 11? Could you check with lspci before you try to shutdown?
> >
> >> [ 66.370656] Pid: 0, comm: swapper Not tainted
> >> 2.6.32.43_guest-1.0.8.kvmguest-default #1
> >> [ 66.370658] Call Trace:
> >> [ 66.370660] <IRQ> [<ffffffff8107b176>] __report_bad_irq+0x26/0xa0
> >> [ 66.370687] [<ffffffff8107b37c>] note_interrupt+0x18c/0x1d0
> >> [ 66.370691] [<ffffffff8107bd4d>] handle_fasteoi_irq+0x13d/0x1c0
> >> [ 66.370701] [<ffffffff8100ee5d>] handle_irq+0x1d/0x30
> >> [ 66.370704] [<ffffffff8100e557>] do_IRQ+0x67/0xe0
> >> [ 66.370708] [<ffffffff8100c813>] ret_from_intr+0x0/0x11
> >> [ 66.370716] [<ffffffff8104ace3>] ? __do_softirq+0x63/0x140
> >> [ 66.370720] [<ffffffff8100cfcc>] ? call_softirq+0x1c/0x30
> >> [ 66.370723] [<ffffffff8100ee05>] ? do_softirq+0x65/0xa0
> >> [ 66.370725] [<ffffffff8104abbd>] ? irq_exit+0x7d/0x90
> >> [ 66.370728] [<ffffffff8100e560>] ? do_IRQ+0x70/0xe0
> >> [ 66.370731] [<ffffffff8100c813>] ? ret_from_intr+0x0/0x11
> >> [ 66.370732] <EOI> [<ffffffff81025586>] ? native_safe_halt+0x6/0x10
> >> [ 66.370747] [<ffffffff81061d65>] ?
> >> atomic_notifier_call_chain+0x15/0x20
> >> [ 66.370753] [<ffffffff81013f27>] ? default_idle+0x27/0x50
> >> [ 66.370757] [<ffffffff8100b036>] ? cpu_idle+0x66/0xc0
> >> [ 66.370772] [<ffffffff81597545>] ? rest_init+0x75/0x80
> >> [ 66.370786] [<ffffffff81840c42>] ? start_kernel+0x2ed/0x2f9
> >> [ 66.370790] [<ffffffff818402f4>] ?
> >> x86_64_start_reservations+0xfb/0xff
> >> [ 66.370793] [<ffffffff818403f2>] ? x86_64_start_kernel+0xfa/0x109
> >> [ 66.370795] handlers:
> >> [ 66.370796] [<ffffffff8133d7c0>] (vp_interrupt+0x0/0x60)
> >> [ 66.370810] Disabling IRQ #11
> >>
> >> 进程:
> >> PID: 1943 TASK: ffff88007da18580 CPU: 0 COMMAND: "halt"
> >> #0 [ffff88007e8b1b98] schedule at ffffffff815b295d
> >> #1 [ffff88007e8b1ca0] schedule_timeout at ffffffff815b358e
> >> #2 [ffff88007e8b1d30] schedule_timeout_uninterruptible at
> >> ffffffff815b36c9
> >> #3 [ffff88007e8b1d40] msleep at ffffffff81050f98
> >> #4 [ffff88007e8b1d50] native_cpu_die at ffffffff8101d81c
> >> #5 [ffff88007e8b1d80] _cpu_down at ffffffff8159840a
> >> #6 [ffff88007e8b1de0] disable_nonboot_cpus at ffffffff810461f2
> >> #7 [ffff88007e8b1e30] kernel_power_off at ffffffff81057321
> >> #8 [ffff88007e8b1e40] sys_reboot at ffffffff810575dc
> >> #9 [ffff88007e8b1f80] system_call_fastpath at ffffffff8100bf02
> >> RIP: 00007f2d9c768c66 RSP: 00007fff4ad666f8 RFLAGS: 00010202
> >> RAX: 00000000000000a9 RBX: ffffffff8100bf02 RCX: 0000000000000000
> >> RDX: 000000004321fedc RSI: 0000000028121969 RDI: fffffffffee1dead
> >> RBP: 0000000000000003 R8: 0000000000000000 R9: ff00000000000000
> >> R10: 00007fff4ad711e0 R11: 0000000000000202 R12: 0000000000000000
> >> R13: 00007fff4ad71690 R14: 0000000000000003 R15: 0000000000000002
> >> ORIG_RAX: 00000000000000a9 CS: 0033 SS: 002b
> >>
> >>
> >>
> >> struct irq_desc {
> >> irq = 11,
> >> timer_rand_state = 0x0,
> >> kstat_irqs = 0xffff88007f80d598,
> >> handle_irq = 0xffffffff8107bc10 <handle_fasteoi_irq>,
> >> chip = 0xffffffff81825e40,
> >> msi_desc = 0x0,
> >> handler_data = 0x0,
> >> chip_data = 0xffffffff817bd4f0,
> >> action = 0xffff88007efda340,
> >> status = 8406528,
> >> depth = 1,
> >> wake_depth = 0,
> >> irq_count = 0,
> >> last_unhandled = 4294908888,
> >> irqs_unhandled = 0,
> >> lock = {
> >> raw_lock = {
> >> {
> >> head_tail = 2532349678,
> >> tickets = {
> >> head = 38638,
> >> tail = 38640
> >> }
> >> }
> >> }
> >> },
> >> affinity = {{
> >> bits = {3, 0}
> >> }},
> >> node = 0,
> >> pending_mask = {{
> >> bits = {0, 0}
> >> }},
> >> threads_active = {
> >> counter = 0
> >> },
> >> wait_for_threads = {
> >> lock = {
> >> raw_lock = {
> >> {
> >> head_tail = 0,
> >> tickets = {
> >> head = 0,
> >> tail = 0
> >> }
> >> }
> >> }
> >> },
> >> task_list = {
> >> next = 0xffffffff817b8ae0,
> >> prev = 0xffffffff817b8ae0
> >> }
> >> },
> >> dir = 0xffff88007f0045c0,
> >> name = 0xffffffff8171cd20 "fasteoi"
> >> }
> >>
> >>
> >>
> >> thanks
> >> yili
> >
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
