[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] x86_64 linux kernel doesn't boot with -icount enabled

From: Cao,Bing Bu
Subject: Re: [Qemu-devel] x86_64 linux kernel doesn't boot with -icount enabled
Date: Wed, 09 Nov 2011 18:42:56 +0800
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110927 Red Hat/3.1.15-1.el6_1 Thunderbird/3.1.15

On 11/09/2011 05:41 PM, Cao,Bing Bu wrote:
On 11/08/2011 11:52 PM, Max Filippov wrote:
With kernel command line of 'console=ttyS0 noapic=1 panic=1' patched
qemu boots up successfully with -icount, whereas unpatched qemu loops

Looks like APIC emulation issue to me.

I'm trying to test issue using a 2.6.38 vmlinuz image.
The image is a kernel image of a another ubuntu guest. I just copy it to host and use it directly.

# /usr/local/bin/qemu-system-x86_64 -enable-kvm -m 1024 -kernel vmlinuz-2.6.38-8-generic -append 'ro quiet noacpi=1 ' -chardev stdio,id=mon0 -mon chardev=mon0

The kernel can be successfully loaded and run normally until kernel_init(),and panic because there is no root file-system supplied.

But add -icount option:

# /usr/local/bin/qemu-system-x86_64 -enable-kvm -m 1024 -kernel vmlinuz-2.6.38-8-generic -append 'root=UUID=96bc04c5-410e-482a-82bf-95b2355552d6 ro quiet noacpi=1' -chardev stdio,id=mon0 -mon chardev=mon0 -icount auto

The kernel can not be loaded successfully.

loop in main_loop_wait().

When with option -icount,kernel message:
"HPET counter not counting. HPET disabled"

halt not continue running:
normally boot message:

<  APIC calibration not consistent with PM-Timer: 92ms instead of 100ms^M
<  APIC delta adjusted to PM-Timer: 6250004 (5750429)^M
< Performance Events: unsupported p6 CPU model 2 no PMU driver, software events only.^M
<  Brought up 1 CPUs^M
<  Total of 1 processors activated (5183.86 BogoMIPS).^M
<  devtmpfs: initialized^M
<  print_constraints: dummy: ^M
<  Time: 10:32:17  Date: 11/09/11^M
<  NET: Registered protocol family 16^M
<  EISA bus registered^M
<  ACPI: bus type pci registered^M
<  PCI: PCI BIOS revision 2.10 entry at 0xffe77, last bus=0^M
<  PCI: Using configuration type 1 for base access^M
<  bio: create slab <bio-0> at 0^M
<  ACPI: Interpreter enabled^M
<  ACPI: (supports S0 S3 S4 S5)^M
<  ACPI: Using IOAPIC for interrupt routing^M
<  ACPI: No dock devices found.^M
<  HEST: Table not found.^M
< PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug^M
<  ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])^M
<  pci 0000:00:01.3: quirk: [io  0xb000-0xb03f] claimed by PIIX4 ACPI^M
<  pci 0000:00:01.3: quirk: [io  0xb100-0xb10f] claimed by PIIX4 SMB^M
<  ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)^M
<  ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)^M
<  ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)^M
<  ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)^M
<  ACPI: PCI Interrupt Link [LNKS] (IRQs 9) *0^M

Maybe right,it is a ACPI issue.

Best Regards,
Cao,Bing Bu

reply via email to

[Prev in Thread] Current Thread [Next in Thread]