WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Dom0 fails to boot on x86_64

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Dom0 fails to boot on x86_64
From: David F Barrera <dfbp@xxxxxxxxxx>
Date: Thu, 19 May 2005 10:10:05 -0500
Delivery-date: Thu, 19 May 2005 15:09:35 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I've been able to build Xen on a FC4 (Beta) platform. It fails to boot,
however, as follows:

Note: there is a similar issue documented in the Xensource Bugzilla
system: 
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=26


Booting 'Xen Domain 0 on a FC4 Linux platform'

kernel (hd0,0)/boot/xen.gz dom0_mem=256000 com2=19200,8n1
console=vga,com2 nore
boot
   [Multiboot-elf, <0x100000:0x562d0:0x1fd30>, shtab=0x176078,
entry=0x100000]
module (hd0,0)/boot/vmlinuz-2.6-xen0 root=/dev/sda1 ro console=tty0
   [Multiboot-module @ 0x177000, 0x635e50 bytes]
module (hd0,0)/boot/initrd-2.6.11-10-xen0
   [Multiboot-module @ 0x7ad000, 0x209c00 bytes]

 __  __            _____  ___         _                _
 \ \/ /___ _ __   |___ / / _ \     __| | _____   _____| |
  \  // _ \ '_ \    |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
  /  \  __/ | | |  ___) | |_| |__| (_| |  __/\ V /  __/ |
 /_/\_\___|_| |_| |____(_)___/    \__,_|\___| \_/ \___|_|

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.0-devel (root@xxxxxxxxxxxxxxxxxx) (gcc version 4.0.0
20050405
(Red Hat 4.0.0-0.40)) Thu May 19 08:43:31 CDT 2005
 Latest ChangeSet: information unavailable
 (XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009d400 (usable) (XEN)
000000000009d400 -
00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved) (XEN)
0000000000100000 -
000000003ffbe680 (usable)
(XEN)  000000003ffbe680 - 000000003ffd0000 (ACPI data)
(XEN)  000000003ffd0000 - 0000000040000000 (reserved)
(XEN)  00000000fec00000 - 0000000100000000 (reserved)
(XEN) System RAM: 1023MB (1047916kB)
(XEN) Xen heap: 14MB (14856kB)
(XEN) CPU0: Before vendor init, caps: bfebfbff 20000800 00000000, vendor
= 0
(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 20000800 00000000 00000000
(XEN) found SMP MP-table at 0009d540
(XEN) ACPI: RSDP (v000 IBM                                   ) @
0x00000000000fdfc0
(XEN) ACPI: RSDT (v001 IBM    SERBLADE <85>(XEN) ACPI: MCFG (v001 IBM   
SERBLADE 0x00001000 IBM  0x45444f43) @ 0x000000003ffcfdc0
(XEN) ACPI: DSDT (v001 IBM    SERBLADE 0x00001000 INTL 0x02002025) @
0x0000000000000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
(XEN) Processor #6 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:Y®®æec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 14, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x0d] address[0xfec10000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 13, version 32, address 0xfec10000, GSI 24-47
(XEN) ACPI: IOAPIC (id[0x0c] address[0xfec81000] gsi_base[48])
(XEN) IOAPIC[2]: apic_id 12, version 32, address 0xfec81000, GSI 48-71
(XEN) ACPI: IOAPIC (id[0x0b] address[0xfec81400] gsi_base[72])
(XEN) IOAPIC[3]: apic_id 11, version 32, address 0xfec81400, GSI(XEN)
Initializing CPU#1
(XEN) CPU1: Before vendor init, caps: bfebfbff 20000800 00000000, vendor
= 0
(XEN) CPU#1: Physical ID: 0, Logical ID: 1
(XEN) CPU caps: bfebfbff 20000800 00000000 00000000
(XEN) CPU1 has booted.
(XEN) Booting processor 2/6 eip 90000
(XEN) Initializing CPU#2
(XEN) CPU2: Before vendor init, caps: bfebfbff 20000800 00000000, vendor
= 0
(XEN) CPU#2: Physical ID: 3, Logical ID: 0
(XEN) CPU caps: bfebfbff 20000800 00000000 00000000
(XEN) CPU2 has booted.
(XEN) Booti(XEN) checking TSC synchronization across CPUs: passed.
(XEN) Time init:
(XEN) .... cpu_freq:    00000000:D6989870
(XEN) .... scale:       00000001:1C6B35D0
(XEN) .... Wall Clock:  1116494635s 310000us
(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_BASE=0xffffffff80100000,LOADER=generic'
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000008000000->0000000010000000 (31232 pages to
be
allo0->ffffffff80c00000
(XEN)  ENTRY ADDRESS: ffffffff80100000
(XEN) Initrd len 0x256800, start at 0xffffffff8052f000
(XEN) Scrubbing Free RAM: ...........done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
(XEN) CPU:    0
(XEN) EIP:    e030:[<0000000000000000>]
(XEN) EFLAGS: 0000000000010202
(XEN) rax: ffffffffffffffff   rbx: 0000000000001f40   rcx:
0000000000000000  
rdx: 0000000000000000
(XEN) rsi: 00000000000000ff   rdi: ffff880000800000   rbp:
ffffffff80469ede  
rsp: ffffffff80104030
(XEN) r8:  ffffffff804773c0   r9:  0000000000000000   r10:
ffff880000800000  
r11: 0000000000000202
(XEN) r12: 000000000000001e   r13: ffffffff8038d871   r14:
ffffffff8038d87c  
r15: ffffffff8038d86c
(XEN) Xen stack trace from rsp=ffffffff80104030:
(XEN)    000000000<82><82><82>^B<82>þ000000000000202 0000000000000000
0000000000000004 0000000000000000 000000000000e030 0000000000010202
ffffffff80104078
(XEN)    000000000000e02b 0000000000000000 0000000000000202
0000000000000000
0000000000000004 0000000000000000 000000000000e030 0000000000010202
(XEN)    ffffffff801040c0 000000000000e02b 0000000000000000
0000000000000202
0000000000000000 0000000000000004 0000000000000000 000000000000e030
(XEN)    0000000000010202 ffffffff80104108 000000000000e02b
0000000000000000
00070 000000000000e02b
(XEN)    0000000000000000 0000000000000202 0000000000000000
0000000000000004
0000000000000000 000000000000e030 0000000000010202 ffffffff801042b8
(XEN)    000000000000e02b 0000000000000000 0000000000000202
0000000000000000
0000000000000004 0000000000000000 000000000000e030 0000000000010202
(XEN)    ffffffff80104300 000000000000e02b 0000000000000000
0000000000000202
0000000000000000 0000000000000004 0000000000000000 000000000000e030
(XEN)    0000000000010202 ffffffff801Ì000 0000000000000004
0000000000000000
000000000000e030 0000000000010202 ffffffff801044f8
(XEN)    000000000000e02b 0000000000000000 0000000000000202
0000000000000000
0000000000000004 0000000000000000 000000000000e030 0000000000010202
(XEN) Xen call trace from rsp=ffffffff80104030:
(XEN)    Trace empty.

****************************************
Panic on CPU0:
Domain 0 crashed!
****************************************

Reboot in five seconds...

-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Dom0 fails to boot on x86_64, David F Barrera <=