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

[Kelvin Middleton <kelvin.middleton@xxxxxxxxx>]

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