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-users] Re: [Xen-devel] Re: How to build a 64 bit xen

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: [Xen-users] Re: [Xen-devel] Re: How to build a 64 bit xen
From: lei yang <yanglei.fage@xxxxxxxxx>
Date: Tue, 18 May 2010 23:26:02 +0800
Cc: George Dunlap <dunlapg@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Xen Mailing List <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 18 May 2010 08:32:09 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=/FDiCmzzOn7f/dacdv3zbEF7h29O7QySIOgZx92owZc=; b=cnQulvUJRtLK9bMT2s/GYbUw5C1OU348NfVlYhtU23IekmD75ToHk3h+WbXXmQtoK3 kfCpL0WQLrNuoGKoVZbVuWodmaHCTwwbO9ku07pi+EZSmV+rpadscpnuF16n6tMYxJS7 ZmgK0I6wwGyYv+xJETWaM0zCNJ6YK7FFhAfM0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=PKrrpzTbcnqQ6AvAguxqKQ7FTeEGJ6t0aioUrF0gCU8VZA/7QnoYy7sKub4+nLYoFE SToX8i2Yf7wg2ZKXOCK4j36c0HvGQlr5IgYpWPtPdZijfEYOqEDY7C03yCynpaSrXxEg L2PnJcpMwLT9KWyY9zvZdhWJAwZLhaqT9iw0o=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1274196015.6180.243.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTiniIuaRT2aaA7DBnjghIvvZ5XMXYrjVKwn7FeY7@xxxxxxxxxxxxxx> <AANLkTinVB-d6Wdmo2fks3acxYBH95FsXRo7M7oOg6yvv@xxxxxxxxxxxxxx> <AANLkTil9HtVDqn9bKWnSCuvTWUQuCBv3kdldAox3ZFRd@xxxxxxxxxxxxxx> <1274196015.6180.243.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
 
It's bad luck for me not to boot with the 64 bit xen( which see its' 32 bit with "file")
my bootloader is gpxe.and don't see any output log, just see the target reboot
 
32 bit xen works well
 
Lei
 
 

 
On Tue, May 18, 2010 at 11:20 PM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
On Tue, 2010-05-18 at 16:13 +0100, George Dunlap wrote:
> I've cross-compiled 64-bit xen exclusively since I've worked for
> XenSource basically.  Here's what I get:
>
> $ file xen/xen
> xen/xen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
> statically linked, stripped
> $ file xen/xen-syms
> xen/xen-syms: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> statically linked, not stripped
>
> So I think 'file' is just making a mistake.

The 64 bit hypervisor really is encapsulated in a 32 bit container, see
the mkelf32 related rules in xen/arch/x86/Makefile.

I'm not sure why. Something to do with 32 bit bootloaders maybe?

Ian




--
"We learn from failure, not from success!"
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users