Re: 2.6.16 Guest Hangs on Boot

Alexander Graf
2010-09-15T18:15:59Z

On 15.09.2010, at 20:07, Alec Joseph Rivera wrote:

> On Wed, 2010-09-15 at 19:51 +0200, Alexander Graf wrote:
>> On 15.09.2010, at 19:48, Alec Joseph Rivera wrote:
>>
>>> On Wed, 2010-09-15 at 19:28 +0200, Alexander Graf wrote:
>>>> On 15.09.2010, at 18:53, Alec Joseph Rivera wrote:
>>>>
>>>>> Hi all:
>>>>>
>>>>> I'm Alec Joseph Rivera, from the Philippines and new on this list.
>>>>> Anyway, I'm trying to run Lotus Foundations on kvm and it just hangs on
>>>>> bootup. It stops right after:
>>>>>
>>>>> Checking if this processor honours the WP bit even in supervisor
>>>>> mode... Ok.
>>>>>
>>>>> There's no more output after that. My invocation line is:
>>>>>
>>>>> $ qemu-kvm -cpu host -m 1G -cdrom lfs.iso
>>>>
>>>> Your host is probably too new for this old guest. -cpu host directly passes through this host cpu's identifiers on which the guest might choke. Please try again without -cpu.
>>>>
>>>>
>>>
>>> Tried without -cpu, still hangs after the WP bit checking...
>>>
>>> $ qemu-kvm -m 1G -cdrom lfs.iso
>>>
>>> I was scanning the changelogs and read something about a
>>> -no-kernel-irqchip. The man page doesn't say anything about it but will
>>> try this one too..
>>
>> Please try:
>>
>> $ qemu-kvm -m 1G -cdrom lfs.iso -serial stdio
>>
>> Then when it shows the bootloader, add "console=ttyS0" to the kernel command line. That should give all the debugging output necessary.
>>
>>
>
> Already done this one too (I've read it from your conversations with a
> Peter guy if I'm not mistaken).
>
> It just stops with no panic messages right after the mentioned checking
> part, which made me dig after timers (bogomips calibration should be
> next I believe). But I've gotten nowhere so far...
>
> Also, there's no -no-kernel-irqchip parameter, must have been a typo for
> -no-kvm-irqchip.
>
> -- begin kernel messages
>> Linux version 2.6.16.54-0.2.5-bigsmp (geeko@buildhost) (gcc version 4.1.2 20070115 (prerelease) (SUSE Linux)) #1 SMP Mon Jan 21 08:29:51 EST 2008
>> BIOS-provided physical RAM map:
>> BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
>> BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
>> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
>> BIOS-e820: 0000000000100000 - 000000003fffd000 (usable)
>> BIOS-e820: 000000003fffd000 - 0000000040000000 (reserved)
>> BIOS-e820: 00000000fffbc000 - 0000000100000000 (reserved)
>> 127MB HIGHMEM available.
>> 895MB LOWMEM available.
>> found SMP MP-table at 000f8990
>> DMI 2.4 present.
>> Using APIC driver default
>> ACPI: PM-Timer IO Port: 0xb008
>> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
>> Processor #0 15:11 APIC version 20
>> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
>> Processor #1 15:11 APIC version 20
>> Overriding APIC driver with bigsmp
>> ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
>> IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
>> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
>> ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
>> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
>> ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
>> ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
>> Enabling APIC mode: Physflat. Using 1 I/O APICs
>> ACPI: HPET id: 0x8086a201 base: 0xfed00000
>> Using ACPI (MADT) for SMP configuration information
>> Allocating PCI resources starting at 50000000 (gap: 40000000:bffbc000)
>> Built 1 zonelists
>> Kernel command line: ramdisk_size=32768 initrd=initrd root=/dev/ram BOOT_IMAGE=k12_1009 console=ttyS0
>> Enabling fast FPU save and restore... done.
>> Enabling unmasked SIMD FPU exception support... done.
>> Initializing CPU#0
>> PID hash table entries: 4096 (order: 12, 65536 bytes)
>> Console: colour VGA+ 80x25
>> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
>> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
>> Memory: 1022272k/1048564k available (1671k kernel code, 25488k reserved, 890k data, 200k init, 131064k highmem)
>> Checking if this processor honours the WP bit even in supervisor mode... Ok.

Interesting. Mind to check if you find a the vmlinux binary for that kernel on the cd? Maybe it's hidden inside an rpm. Then you can use:

$ qemu-kvm -s -cdrom ...
$ gdb <vmlinux> -ex 'target remote localhost:1234'

(gdb) bt

That should give us a clue on what's going wrong.

Also, does the host's dmesg say anything?

Alex