Re: [Xen-devel] Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2

[Eric Shelton <eshelton@xxxxxxxxx>]

Kevin,

I do not know if you got EFI working, but I am successfully botting
Xen under EFI; however, I ended up patching the dom0 kernel in order
to get it all working.  The patches, which were mostly a rebase of an
earlier patchset, are available here:

http://lists.xen.org/archives/html/xen-devel/2013-05/msg02492.html

You will find it straightforward to update the patch for Linux 3.10.
I believe CONFIG_EFI has to be set in the config.

I continue to use these patches to boot a Linux 3.10.1 dom0 under EFI
Xen, which is started by the rEFInd boot manager.  The patches have
the added benefit in that you can generate a single Linux kernel which
can boot either standalone under EFI or under Xen booting under EFI.
The only shortcoming I have observed with my setup is that dom0
shutdown will shut down the computer, but a dom0 reboot does not get
the underlying hardware to reboot - instead it must be power cycled.

Although the above patches definitely work for me, I no longer recall
if dom0 MUST have such patches to work under EFI booting of Xen.  For
example, even when booting under EFI, Xen might provide enough of a
BIOS-boot-like environment that a vanilla kernel can successfully find
and configure the system hardware.  I think I ended up going down this
path because of (1) successful handof of the EFI console to dom0,
and/or (2) I am running on a Mac, which is very finicky and quirky for
booting up non-OS X operating systems.

Best of luck,
Eric

> Date: Mon, 15 Jul 2013 21:37:46 +0100
> From: Kelvin Middleton <kelvin.middleton@xxxxxxxxx>
> To: Kristian Hagsted Rasmussen <kristian@xxxxxxxxxx>
> Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>,
>         Jan Beulich <JBeulich@xxxxxxxx>
> Subject: Re: [Xen-devel] Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2
>
> Hi Jan, Hi Kristian, thanks for the feedback & help.
>
> For EFI_VENDOR I've now corrected my build step to be "make install-xen
> EFI_VENDOR=EFI/ubuntu EFI_MOUNTPOINT=/boot/" and this puts all the files
> where they should be.
>
> The .cfg file I think you'll say is a school-boy error....I was using the
> debug EFI shell that Virtualbox provides to create the .cfg file.  Turns
> out this is just wrong as I recreated the file once in ubuntu bash and Xen
> attempted to load the Dom0 kernel image.
>
> I'm now getting Xen boot kernel screen output but I have a new problem
> which is a kernel panic and a hang, progress though so I'm pretty happy.
>
> Kernel Panic is...
>
> do_device_not_available
>
> ******************************
> Panic on CPU 0:
> Xen BUG at traps.c: 3393
> ******************************
>
> Some googling on this error seems to point to the FPU setup (don't really
> know what this is) http://copilotco.com/mail-archives/xen.2008/msg14478.html
> ??
>
> On 15 July 2013 16:57, Kristian Hagsted Rasmussen <kristian@xxxxxxxxxx>wrote:
>
> >
> >
> > > -----Original Message-----
> > > From: xen-devel-bounces@xxxxxxxxxxxxx [mailto:xen-devel-
> > > bounces@xxxxxxxxxxxxx] On Behalf Of Jan Beulich
> > > Sent: 15. juli 2013 11:35
> > > To: Kelvin Middleton; Kristian Hagsted Rasmussen
> > > Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx
> > > Subject: Re: [Xen-devel] Building Xen 4.2.2 w/EFI on Ubuntu Server
> > 12.04.2
> > >
> > > >>> On 15.07.13 at 11:10, Kristian Hagsted Rasmussen <
> > kristian@xxxxxxxxxx>
> > > wrote:
> > > >> From: Jan Beulich [mailto:JBeulich@xxxxxxxx]
> > > >> Sent: 15. juli 2013 10:03
> > > >> To: Kelvin Middleton; Kristian Hagsted Rasmussen
> > > >> Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx
> > > >> Subject: RE: [Xen-devel] Building Xen 4.2.2 w/EFI on Ubuntu Server
> > > >> 12.04.2
> > > >>
> > > >> >>> On 15.07.13 at 09:48, Kristian Hagsted Rasmussen
> > > >> >>> <kristian@xxxxxxxxxx>
> > > >> wrote:
> > > >> >> > [global]
> > > >> >> > default=xen
> > > >> >> >
> > > >> >> > [xen]
> > > >> >> > options=console=vga loglvl=all noreboot
> > > >> >> > kernel=vmlinuz-3.5.0-36-
generic ignore_loglevel
> > > >> >> > ramdisk=initrd-3.5.0-36-generic
> >
> > Are you sure your ramdisk image is called
> > initrd-3.5.0-36-generic
> > and not:
> > initrd.img-3.5.0-36-generic
> > Which seems to be the name on my Ubuntu system.
> >
> > Best regards Kristian Hagsted Rasmussen
> >

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel