From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Xen support for native EFI boot Date: Fri, 02 Mar 2012 08:22:05 +0000 Message-ID: References: <4F508D7F0200007800075EDC@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F508D7F0200007800075EDC@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , Joseph Cihula Cc: Gang Wei , xen-devel List-Id: xen-devel@lists.xenproject.org On 02/03/2012 08:06, "Jan Beulich" wrote: >>>> On 01.03.12 at 21:40, "Cihula, Joseph" wrote: >> Can someone provide instructions and the necessary environment/toolchain >> support needed to get Xen to build and boot on a native EFI system (i.e. with >> no CSM/legacy support)? > > gcc must be 4.5.x or newer (I'd recommend not trying anything below > 4.6.x, as I'm unaware of anyone ever having tried that, and I can't > exclude that there are bugs in the relevant code that was newly added > in 4.5.0). > > ld must support linking native 64-bit EFI applications, which so far no > released binutils version does. The single relevant change that's > necessary for this to work in 2.21 can be taken from > http://www.sourceware.org/ml/binutils/2011-05/msg00131.html (but > there's at least one other non-essential adjustment in case you want > to do anything with the generated binary that involves its symbol > table). Has that patch been picked up by the maintainers? -- Keir > Next, a suitably enabled Dom0 kernel is needed. > > Finally, a config file needs to be placed alongside the xen*.efi > binary; I'm attaching a simplistic example. > > Jan >