Subrahmanian, Raj
2005-Jul-19 05:16 UTC
[Xen-devel] Problems booting 32-bit Domain 0 and 32 bit Xen on x86_64 hardware
All, I am running on x86_64 hardware, but running it in 32 bit mode, i.e., all the software and the Linux (Suse Sles 9) is in 32 bit. The box has two Intel Xeon EMT64 procs with hyperthreading enabled with 2 Gigs of RAM. I find that when I install and run xen (the unstable build ChangeSet: Sat Jul 16 12:45:24 2005 722c372fe2017414acd568874a313a8f5e8685f5) the system crashes on Dom0 boot. I am running the 2.6.11 kernel for Dom0 Here is the relevant dump, from the serial output. At this point, I tried to attach gdb, but without success. Raj __ _____ ___ _ _ \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | \ // _ \ ''_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ | / \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ | /_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_| http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 3.0-devel (root@site) (gcc version 3.3.3 (SuSE Linux)) Tue Jul 19 0 0:02:04 EDT 2005 Latest ChangeSet: Sat Jul 16 12:45:24 2005 722c372fe2017414acd568874a313a8f5e86 85f5 (XEN) Physical RAM map: (XEN) 0000000000000000 - 00000000000a0000 (usable) (XEN) 00000000000f0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000007fe8ac00 (usable) (XEN) 000000007fe8ac00 - 000000007fe8cc00 (ACPI NVS) (XEN) 000000007fe8cc00 - 000000007fe8ec00 (ACPI data) (XEN) 000000007fe8ec00 - 0000000080000000 (reserved) (XEN) 00000000e0000000 - 00000000f0000000 (reserved) (XEN) 00000000fec00000 - 00000000fed00400 (reserved) (XEN) 00000000fed20000 - 00000000feda0000 (reserved) (XEN) 00000000fee00000 - 00000000fef00000 (reserved) (XEN) 00000000ffb00000 - 0000000100000000 (reserved) (XEN) System RAM: 2046MB (2095272kB) (XEN) Xen heap: 10MB (10588kB) (XEN) PAE disabled. (XEN) found SMP MP-table at 000fe710 (XEN) DMI 2.3 present. (XEN) Using APIC driver default (XEN) ACPI: RSDP (v000 DELL ) @ 0x000febf0 (XEN) ACPI: RSDT (v001 DELL WS 470 0x00000007 ASL 0x00000061) @ 0x000fcb98 (XEN) ACPI: FADT (v001 DELL WS 470 0x00000007 ASL 0x00000061) @ 0x000fcbd8 (XEN) ACPI: SSDT (v001 DELL st_ex 0x00001000 MSFT 0x0100000d) @ 0xfffc4413 (XEN) ACPI: MADT (v001 DELL WS 470 0x00000007 ASL 0x00000061) @ 0x000fcc4c (XEN) ACPI: BOOT (v001 DELL WS 470 0x00000007 ASL 0x00000061) @ 0x000fccd6 (XEN) ACPI: ASF! (v016 DELL WS 470 0x00000007 ASL 0x00000061) @ 0x000fccfe (XEN) ACPI: MCFG (v001 DELL WS 470 0x00000007 ASL 0x00000061) @ 0x000fcd65 (XEN) ACPI: HPET (v001 DELL WS 470 0x00000007 ASL 0x00000061) @ 0x000fcda3 (XEN) ACPI: DSDT (v001 DELL dt_ex 0x00001000 MSFT 0x0100000d) @ 0x00000000 (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) Processor #0 15:3 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled) (XEN) Processor #6 15:3 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled) (XEN) Processor #1 15:3 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled) (XEN) Processor #7 15:3 APIC version 20 (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: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24]) (XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47 (XEN) ACPI: IOAPIC (id[0x0a] address[0xfec80800] gsi_base[48]) (XEN) IOAPIC[2]: apic_id 10, version 32, address 0xfec80800, GSI 48-71 (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) Using ACPI (MADT) for SMP configuration information (XEN) Initializing CPU#0 (XEN) Detected 2992.626 MHz processor. (XEN) Using scheduler: Simple EDF Scheduler (sedf) (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K (XEN) CPU: L2 cache: 1024K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU0: Intel(R) Xeon(TM) CPU 3.00GHz stepping 04 (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: 1024K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU1: Intel(R) Xeon(TM) CPU 3.00GHz stepping 04 (XEN) Booting processor 2/6 eip 90000 (XEN) Initializing CPU#2 (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K (XEN) CPU: L2 cache: 1024K (XEN) CPU: Physical Processor ID: 3 (XEN) CPU2: Intel(R) Xeon(TM) CPU 3.00GHz stepping 04 (XEN) Booting processor 3/7 eip 90000 (XEN) Initializing CPU#3 (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K (XEN) CPU: L2 cache: 1024K (XEN) CPU: Physical Processor ID: 3 (XEN) CPU3: Intel(R) Xeon(TM) CPU 3.00GHz stepping 04 (XEN) Total of 4 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1 (XEN) checking TSC synchronization across 4 CPUs: passed. (XEN) Time init: (XEN) .... cpu_freq: 00000000:B25FDB1C (XEN) .... scale: 00000001:562CA1E6 (XEN) .... Wall Clock: 1121745978s 130000us (XEN) Brought up 4 CPUs (XEN) Xendbg initialised. (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE0xC0000000,LOADER=generic'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 20000000->40000000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c05d2bc4 (XEN) Init. ramdisk: c05d3000->c05d3000 (XEN) Phys-Mach map: c05d3000->c0653000 (XEN) Page tables: c0653000->c0656000 (XEN) Start info: c0656000->c0657000 (XEN) Boot stack: c0657000->c0658000 (XEN) TOTAL: c0000000->c0800000 (XEN) ENTRY ADDRESS: c0100000 (XEN) Scrubbing Free RAM: .....................done. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen ). (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) CPU: 0 (XEN) EIP: e019:[<c010000d>] (XEN) EFLAGS: 00000282 CONTEXT: guest (XEN) eax: 00000000 ebx: 00000000 ecx: 00000000 edx: 00000000 (XEN) esi: c0656200 edi: c0597620 ebp: 00000000 esp: c0657ff0 (XEN) cr0: 8005003b cr3: 20653000 (XEN) ds: e021 es: e021 fs: e021 gs: e021 ss: e021 cs: e019 (XEN) Guest stack trace from esp=c0657ff0: (XEN) 00000820 c010000d 0001e019 00010282 (XEN) Waiting for GDB to attach to XenDBG _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2005-Jul-19 06:03 UTC
Re: [Xen-devel] Problems booting 32-bit Domain 0 and 32 bit Xen on x86_64 hardware
On 19 Jul 2005, at 06:16, Subrahmanian, Raj wrote:> I am running on x86_64 hardware, but running it in 32 bit mode, i.e., > all the software and the Linux (Suse Sles 9) is in 32 bit. > > The box has two Intel Xeon EMT64 procs with hyperthreading enabled > with 2 Gigs of RAM. > I find that when I install and run xen (the unstable build ChangeSet: > Sat Jul 16 12:45:24 2005 722c372fe2017414acd568874a313a8f5e8685f5) the > system crashes on Dom0 boot. > I am running the 2.6.11 kernel for Dom0 > > Here is the relevant dump, from the serial output. > At this point, I tried to attach gdb, but without success.You need to run a matched dom0. Older dom0''s (like your 2.6.11 must be) will not work. We don;t keep backward compatibility in the unstable tree, only during stable series. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Subrahmanian, Raj
2005-Jul-19 14:46 UTC
RE: [Xen-devel] Problems booting 32-bit Domain 0 and 32 bit Xen on x86_64 hardware
Sorry, my mistake. I am having this problem with the matched dom0 (the 2.6.12. kernel). So, I don''t think that compatibility is the issue. Raj -----Original Message----- From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] Sent: Tuesday, July 19, 2005 2:04 AM To: Subrahmanian, Raj Cc: xen-devel@lists.xensource.com; Vessey, Bruce A Subject: Re: [Xen-devel] Problems booting 32-bit Domain 0 and 32 bit Xen on x86_64 hardware On 19 Jul 2005, at 06:16, Subrahmanian, Raj wrote:> I am running on x86_64 hardware, but running it in 32 bit mode, i.e., > all the software and the Linux (Suse Sles 9) is in 32 bit. > > The box has two Intel Xeon EMT64 procs with hyperthreading enabled > with 2 Gigs of RAM. > I find that when I install and run xen (the unstable build ChangeSet: > Sat Jul 16 12:45:24 2005 722c372fe2017414acd568874a313a8f5e8685f5) the > system crashes on Dom0 boot. > I am running the 2.6.11 kernel for Dom0 > > Here is the relevant dump, from the serial output. > At this point, I tried to attach gdb, but without success.You need to run a matched dom0. Older dom0''s (like your 2.6.11 must be) will not work. We don;t keep backward compatibility in the unstable tree, only during stable series. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Subrahmanian, Raj
2005-Jul-19 15:36 UTC
RE: [Xen-devel] Problems booting 32-bit Domain 0 and 32 bit Xen on x86_64 hardware
My mistake again. It was indeed the compatibility issue. I was trying to run the wrong Dom0. Raj -----Original Message----- From: Subrahmanian, Raj Sent: Tuesday, July 19, 2005 10:46 AM To: ''Keir Fraser'' Cc: xen-devel@lists.xensource.com; Vessey, Bruce A; Puthiyaparambil, Aravindh; Davis, Jason; Magolan, John F Subject: RE: [Xen-devel] Problems booting 32-bit Domain 0 and 32 bit Xen on x86_64 hardware Sorry, my mistake. I am having this problem with the matched dom0 (the 2.6.12. kernel). So, I don''t think that compatibility is the issue. Raj -----Original Message----- From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] Sent: Tuesday, July 19, 2005 2:04 AM To: Subrahmanian, Raj Cc: xen-devel@lists.xensource.com; Vessey, Bruce A Subject: Re: [Xen-devel] Problems booting 32-bit Domain 0 and 32 bit Xen on x86_64 hardware On 19 Jul 2005, at 06:16, Subrahmanian, Raj wrote:> I am running on x86_64 hardware, but running it in 32 bit mode, i.e., > all the software and the Linux (Suse Sles 9) is in 32 bit. > > The box has two Intel Xeon EMT64 procs with hyperthreading enabled > with 2 Gigs of RAM. > I find that when I install and run xen (the unstable build ChangeSet: > Sat Jul 16 12:45:24 2005 722c372fe2017414acd568874a313a8f5e8685f5) the > system crashes on Dom0 boot. > I am running the 2.6.11 kernel for Dom0 > > Here is the relevant dump, from the serial output. > At this point, I tried to attach gdb, but without success.You need to run a matched dom0. Older dom0''s (like your 2.6.11 must be) will not work. We don;t keep backward compatibility in the unstable tree, only during stable series. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel