|
xen-devel
Re: [Xen-devel] Latest bk can NOT compile on x86_64
OK. This is the first time that I've been able to build Xen on SLES 9
x86_64. When attempting to boot, Dom0 crashes. Although there is already
a defect open (Bugzilla #26) for a failure to boot Dom0 on x86_64 on
FC4, I am opening a new defect (Bugzilla #65) since the failures appear
different.
__ __ _____ ___ _ _
\ \/ /___ _ __ |___ / / _ \ __| | _____ _____| |
\ // _ \ '_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
/ \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ |
/_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_|
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0-devel (root@xxxxxxxxxxxxxxxxxx) (gcc version 3.3.3 (SuSE
Linux)) Tue May 31 06:20:43 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 (14804kB)
(XEN) found SMP MP-table at 0009d540
(XEN) DMI 2.3 present.
(XEN) Using APICSH\uffff(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:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
(XEN) Processor #7 15:4 APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI
(acpi_i9\uffff\u0455\uffff\u0455\uffff5!\uffff\uffff\u027d\uffff\uffff\uffff\u037d\uffffXEN)
Using scheduler: Borrowed Virtual Time (bvt)
(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.60GHz stepping 01
(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.60GHz stepping 01
(XEN) Booting proc
AU!\uffff\uffff\u0455\uffff\uffff\uffff\uffff\uffffXEN) 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:D6980F54
(XEN) .... scale: 00000001:1C6BEB88
(XEN) .... Wall Clock: 1117540311s 180000us
(XEN) Brought up 4 CPUs
(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.: 0000000010000000->0000000020000000 (62464 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80100000->ffffffff80576086
(XEN) Init. ramdisk: ffffffff80577000->ffffffff80577000
(XEN) Phys-Mach map: ffffffff80577000->ffffffff805f4000
(XEN) Page tables: ffffffff805f4000->ffffffff805fb000
(XEN) Start info: ffffffff805fb000->ffffffff805fc000
(XEN) Boot stack: ffffffff805fc000->ffffffff805fd000
(XEN) TOTAL: ffffffff80000000->ffffffff80800000
(XEN) ENTRY ADDRESS: ffffffff80100000
(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: 0000000000010282
(XEN) rax: 00000000ffffffea rbx: 00000000105f5000 rcx: 0000000000000000
rdx: 0000000000000000
(XEN) rsi: 0000000000000001 rdi: ffffffff804ebf40 rbp: 0000000000000808
rsp: ffffffff804ebf08
(XEN) r8: 0000000000000000 r9: 0000000000000000 r10: 0000000000007ff0
r11: 0000000000000282
(XEN) r12: 0000000000000000 r13: ffffffff805f4000 r14: ffffffff80102000
r15: ffffffff804ebfb0
(XEN) Xen stack trace from rsp=ffffffff804ebf08:
(XEN) ffffffff80118d9d 0000000000000202 ffffffff80118da1 000000000001e030
0000000000010282 ffffffff804ebf40 000000000000e02b 00000000105f5808
(XEN) 0000000010101065 0000000000000000 ffffffff80115d08 0000000000000000
0000000000000000 ffffffff804d8080 ffffffff80 on CPU0:
Domain 0 crashed!
****************************************
Reboot in five seconds...
(XEN) Reboot disabled on cmdline: require manual reset
On Tue, 2005-05-31 at 16:49 +0100, Keir Fraser wrote:
> On 31 May 2005, at 16:16, David F Barrera wrote:
>
> > Using the latest source from BK, on x86_64 SLES 9 installation, I am
> > seeing this error:
> >
> > gcc -Wl,-T,/tmp/xen-unstable/tools/ioemu/x86_64.ld -o qemu-dm vl.o
> > exec.o
> > monitor.o osdep.o block.o readline.o pci.o console.o block-cloop.o
> > ide.o
> > ne2000.o pckbd.o vga.o dma.o fdc.o mc146818rtc.o serial.o i8259.o
> > i8254.o pc.o
> > port-e9.o cirrus_vga.o libqemu.a -lm -L../../libxc -lxc -lz -lutil
> > /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../x86_64-suse-
> > linux/bin/ld:/tmp/xen-unstable/tools/ioemu/x86_64.ld:62:
> > syntax error
>
> We should not have to be specially linking qemu-dm for x86/64 at all.
> The x86/32 excuse of inadequate address space to map all the foreign
> domain's pages does not hold on x86/64.
>
> Would it break anything simply to remove the linker script for x86/64?
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
--
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
|
|
|
Home