[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Problem Booting up a Xen kernel
Hi all! I've experienced some problems. I replaced a function in the Xen version of Linux with its modified version to patch something. Then I built the kernel at /local-home/shlomif/Download/Arcs/Xen/Xen-Enterprise/from-sources/xs-xen/xs-xen-4991b3f7314e/linux-2.6.16.29-xen I scp'ed the vmlinuz and the /lib/modules/linux-2.6.16.29-xen directory to the Xen directory, built an initrd and configured the following entry in /boot/grub/menu.lst: <<<<<<<<<<< title XenTehuti (Serieal) root (hd0,0) kernel /boot/xen-3.0.3.0.gz com1=115200,8n1 console=com1,tty dom0_mem=524288 lowmem_emergency_pool=16M module /boot/vmlinuz-tehuti1 root=LABEL=/-main ro console=tty0 console=ttyS0, 115200n8 module /boot/initrd-tehuti1 However, when booting it I'm getting a long dump on the serial console: <<<<<<<<<<<<<<< (XEN) Domain 0 shutdown: rebooting machine. __ __ _____ ___ _____ ___ \ \/ /___ _ __ |___ / / _ \ |___ / / _ \ \ // _ \ '_ \ |_ \| | | | |_ \| | | | / \ __/ | | | ___) | |_| | ___) | |_| | /_/\_\___|_| |_| |____(_)___(_)____(_)___/ http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 3.0.3.0 (root@xxxxxxxxxxxxxxxxxxxx) (gcc version 3.4.5 20051201 (R6 Latest ChangeSet: 4991b3f7314e.21428d22757d (3.1.0.289.2650) (XEN) Command line: /boot/xen-3.0.3.0.gz com1=115200,8n1 console=com1,tty dom0_M(XEN) Physical RAM map: (XEN) 0000000000000000 - 00000000000a0000 (usable) (XEN) 0000000000100000 - 000000003ffc0000 (usable) (XEN) 000000003ffc0000 - 000000003ffcfc00 (ACPI data) (XEN) 000000003ffcfc00 - 000000003ffff000 (reserved) (XEN) 00000000e0000000 - 00000000fec90000 (reserved) (XEN) 00000000fed00000 - 00000000fed00400 (reserved) (XEN) 00000000fee00000 - 00000000fee10000 (reserved) (XEN) 00000000ffb00000 - 0000000100000000 (reserved) (XEN) System RAM: 1023MB (1047936kB) (XEN) Xen heap: 10MB (10380kB) (XEN) PAE enabled, limit: 16 GB (XEN) found SMP MP-table at 000fe710 (XEN) DMI 2.3 present. (XEN) Using APIC driver default (XEN) ACPI: RSDP (v000 DELL ) @ 0x000fd650 (XEN) ACPI: RSDT (v001 DELL PE1800 0x00000001 MSFT 0x0100000a) @ 0x000fd664 (XEN) ACPI: FADT (v001 DELL PE1800 0x00000001 MSFT 0x0100000a) @ 0x000fd6b0 (XEN) ACPI: MADT (v001 DELL PE1800 0x00000001 MSFT 0x0100000a) @ 0x000fd724 (XEN) ACPI: SPCR (v001 DELL PE1800 0x00000001 MSFT 0x0100000a) @ 0x000fd7c0 (XEN) ACPI: HPET (v001 DELL PE1800 0x00000001 MSFT 0x0100000a) @ 0x000fd810 (XEN) ACPI: MCFG (v001 DELL PE1800 0x00000001 MSFT 0x0100000a) @ 0x000fd848 (XEN) ACPI: DSDT (v001 DELL PE1800 0x00000001 MSFT 0x0100000e) @ 0x00000000 (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[0x01] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: IOAPIC (id[0x03] address[0xfec80000] gsi_base[32]) (XEN) IOAPIC[1]: apic_id 3, version 32, address 0xfec80000, GSI 32-55 (XEN) ACPI: IOAPIC (id[0x04] address[0xfec80800] gsi_base[64]) (XEN) IOAPIC[2]: apic_id 4, version 32, address 0xfec80800, GSI 64-87 (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 3 I/O APICs (XEN) ACPI: HPET id: 0xffffffff base: 0xfed00000 (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 2992.605 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) Xeon(TM) CPU 3.00GHz 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) Xeon(TM) CPU 3.00GHz 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) PAE mode mismatch between Xen and DOM0 (xen=yes, dom0=no) (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) Could not set up DOM0 guest OS (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... Is there anything I'm doing wrong? What can I do to resolve the problem? Regards, Shlomi Fish ------------------------------------------ Shlomi Fish http://www.shlomifish.org/ If his programming is anything like his philosophising, he would find 10 imaginary bugs in the "Hello World" program. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |