This parameter is already on the module line of the config file.
Below is the Grub boot entry:
title Xen 3.0.3 / Ubuntu 2.6.16.29
root (hd0,2)
kernel /boot/xen-3.gz dom0_mem=1048576 noreboot com1=115200,8n1
module /boot/vmlinuz-2.6-xen0 root=/dev/sda3 console=ttyS0,115200
max_loop=64 ro quiet splash
module /boot/initrd.img-2.6.16.29-xen0
savedefault
boot
Is there anything else that I can trace?
Armand
the original trace is repeated below
_________________________________________________________________________
__ __ _____ ___ _____ ___
\ \/ /___ _ __ |___ / / _ \ |___ / / _ \
\ // _ \ '_ \ |_ \| | | | |_ \ __| | | |
/ \ __/ | | | ___) | |_| | ___) |__| |_| |
/_/\_\___|_| |_| |____(_)___(_)____/ \___/
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0.3-0 (root@xxxxxxxxxxxx) (gcc version 4.1.2 20060928
(prerelease) (Ubuntu 4.1.1-13ubuntu5)) Fri Dec 22 14:53:08 CET 2006
Latest ChangeSet: unavailable
(XEN) Command line: /boot/xen-3.gz dom0_mem=1048576 noreboot com1=115200,8n1
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 00000000000a0000 (usable)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000dfe86c00 (usable)
(XEN) 00000000dfe86c00 - 00000000dfe88c00 (ACPI NVS)
(XEN) 00000000dfe88c00 - 00000000dfe8ac00 (ACPI data)
(XEN) 00000000dfe8ac00 - 00000000e0000000 (reserved)
(XEN) 00000000f0000000 - 00000000f4000000 (reserved)
(XEN) 00000000fec00000 - 00000000fed00400 (reserved)
(XEN) 00000000fed20000 - 00000000feda0000 (reserved)
(XEN) 00000000fee00000 - 00000000fef00000 (reserved)
(XEN) 00000000ffb00000 - 0000000100000000 (reserved)
(XEN) System RAM: 3582MB (3668120kB)
(XEN) Xen heap: 13MB (14196kB)
(XEN) found SMP MP-table at 000fe710
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v002 DELL ) @
0x00000000000feb00
(XEN) ACPI: XSDT (v001 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd259
(XEN) ACPI: FADT (v003 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd351
(XEN) ACPI: SSDT (v001 DELL st_ex 0x00001000 INTL 0x20050309) @
0x00000000fffd86d6
(XEN) ACPI: MADT (v001 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd445
(XEN) ACPI: BOOT (v001 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd4b7
(XEN) ACPI: ASF! (v016 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd4df
(XEN) ACPI: MCFG (v001 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd546
(XEN) ACPI: HPET (v001 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd584
(XEN) ACPI: DSDT (v001 DELL dt_ex 0x00001000 INTL 0x20050309) @
0x0000000000000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
(XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 3192.202 MHz processor.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 2048K
(XEN) CPU: Physical Processor ID: 0
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU0: Thermal monitoring enabled
(XEN) CPU0: Intel(R) Pentium(R) 4 CPU 3.20GHz stepping 03
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 2048K
(XEN) CPU: Physical Processor ID: 0
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU1: Thermal monitoring enabled
(XEN) CPU1: Intel(R) Pentium(R) 4 CPU 3.20GHz stepping 03
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) Machine check exception polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Domain 0 kernel supports features = { 0000001f }.
(XEN) Domain 0 kernel requires features = { 00000000 }.
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000006000000->0000000008000000 (253952 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80100000->ffffffff806f36e8
(XEN) Init. ramdisk: ffffffff806f4000->ffffffff80f0d800
(XEN) Phys-Mach map: ffffffff80f0e000->ffffffff8110e000
(XEN) Start info: ffffffff8110e000->ffffffff8110e49c
(XEN) Page tables: ffffffff8110f000->ffffffff8111c000
(XEN) Boot stack: ffffffff8111c000->ffffffff8111d000
(XEN) TOTAL: ffffffff80000000->ffffffff81400000
(XEN) ENTRY ADDRESS: ffffffff80100000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Initrd len 0x819800, start at 0xffffffff806f4000
(XEN) Scrubbing Free RAM: ....................................done.
(XEN) Xen trace buffers: disabled
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0.3-0 x86_64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e033:[<ffffffff80129fc8>]
(XEN) RFLAGS: 0000000000000286 CONTEXT: guest
(XEN) rax: ffffffff805dbf00 rbx: 0000000000000000 rcx: 0000000000000000
(XEN) rdx: 0000000000000100 rsi: ffffffff805dbee0 rdi: ffffffff80497128
(XEN) rbp: ffffffff805dbed0 rsp: ffffffff805dbe10 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000006f0
(XEN) cr3: 0000000006101000 cr2: 0000000000000028
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
(XEN) Guest stack trace from rsp=ffffffff805dbe10:
(XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff80129fc8
(XEN) 000000010000e030 0000000000010086 ffffffff805dbe50 000000000000e02b
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) ffffffff805dbfb0 ffffffff8012a347 0000003000000008 ffffffff805dbfc0
(XEN) ffffffff805dbf00 0000000000000000 0000000000000000 ffffffff8062e040
(XEN) 0000000000000100 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000102 0000000000000000 0000000000000102 ffffffff8011b321
(XEN) 0000000006102ff8 0000000000000000 0000000000000102 ffffffff8011b401
(XEN) 000000000000000f 0000000000006102 ffffffff805c7000 0000000000000000
(XEN) ffffffff805dbfb0 ffffffff80111032 0000000000000000 0000000000000000
(XEN) ffffffff805dbff0 ffffffff805dd11e ffff800000000000 ffff804000000000
(XEN) 00000007ffffffff 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000
(XEN) Domain 0 crashed: 'noreboot' set - not rebooting.
On 24/12/06 9:04 am, "armand.puccetti" <armand.puccetti@xxxxxxxxxx> wrote:
After buying & installing a serial cable, the trace of the boot process,
in which XEN 3.0.3-0 (compiled fom source) gets stuck at boot time is below.
Any idea welcome on what this might be due to!!
Please add console=ttyS0 to the module line of your GRUB config. This is a
boot parameter to Linux to cause its boot output to appear on your serial
line. Currently that is missing so we cannot diagnose the problem. Hopefully
the crash is not so early that there is no boot output to be seen.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
| 
Home