[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Why " When I want to build a 64 bit xen, but I got a 32 bit one"

  • To: Xen Mailing List <xen-users@xxxxxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: lei yang <yanglei.fage@xxxxxxxxx>
  • Date: Tue, 18 May 2010 16:26:06 +0800
  • Cc:
  • Delivery-date: Tue, 18 May 2010 01:27:33 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=QeTULkjRdBTFZBxfVE/qIRqenQVTmKadlFFp9q9cf+nD6NjJj/gkX3hahhPIYzIiy4 jn0gsBZvpsTDasLvwy72JpBECcEfZcYpwK7c/fXZOl7f3rQhTgSTKbSQPVl7tKJ9LQu8 /heY6PDdY5BNJBjehm18WjauTDXo5c3T3CshQ=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi experts,

I want to cross the xen-4.0.0 to 64 bit, and build with

make  CROSS_COMPILE=/home/bin/i586-linux-gnu-x86_64-glibc_std-    XEN_TARGET_ARCH=x86_64   xen

Then I got xen image:
but when I run " file xen"

$ file xen-syms
xen-syms: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), statically linked, not stripped

$ file xen
xen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped

It's a 32 bit one,

From the log I see "./boot/mkelf32 /buildarea1/lyang0/xen/xen-4.0.0/xen/xen-syms /buildarea1/lyang0/xen/xen-4.0.0/xen/xen 0x100000 "
why it change to 32 bit?

and I use this image to boot, it casue the board reboot, and no log output.( I use gpxe boot)
if I build a 32 bit xen (using XEN_TARGET_ARCH=x86_32), it boot well

Any help would be appreciated


"We learn from failure, not from success!"

Attachment: xen_build.log
Description: Binary data

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.