From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Deegan Subject: Re: [Xen-devel] Re: How to build a 64 bit xen Date: Tue, 18 May 2010 16:30:01 +0100 Message-ID: <20100518153001.GI4164@whitby.uk.xensource.com> References: <1274196015.6180.243.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Return-path: Content-Disposition: inline In-Reply-To: <1274196015.6180.243.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: Ian Campbell Cc: lei yang , George Dunlap , "xen-devel@lists.xensource.com" , Xen, List List-Id: xen-devel@lists.xenproject.org At 16:20 +0100 on 18 May (1274199615), Ian Campbell 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? Yep. The Multiboot standard specifies that the kernel should be started in 32-bit protected mode with flat 4GB segments. Xen bootstraps itself from there up into 64-bit mode. Tim. -- Tim Deegan Principal Software Engineer, XenServer Engineering Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)