Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2

Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2

[Kelvin Middleton]

[-- Attachment #1.1: Type: text/plain, Size: 1012 bytes --]

Hi, very new with Xen so am learning as I go.

Have rebuilt binutils to enable i386pep and "ld -V" confirms as such.

I can build xen without error but how should I be passing in the EFI_Vendor
parameter?  I'm currently having to cp the xen-4.2.2.efi from
/usr/lib64/efi/ into my /boot/efi/EFI/ubuntu dir.

(Expecting that my EFI_VENDOR parameter should be "EFI/ubuntu".)

Have created a xen-4.2.2.cfg file in /boot/efi/EFI/ubuntu right next to the
.efi.  Boot shows its using the .cfg file but I get an error about no Dom0
Kernel could be found.  I'm struggling to find or maybe understand the
documentation/posts on this.  My xen-4.2.2.cfg is as follows...

[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

I've cp the kernel and ramdisk files into the same location as the
.efi.  Please can someone point me at the right words to
research/advise where I'm going wrong.  Any help apprecaited.

Thanks,

Kelvin

[-- Attachment #1.2: Type: text/html, Size: 1486 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2

[Jan Beulich]

>>> On 13.07.13 at 16:59, Kelvin Middleton <kelvin.middleton@gmail.com> wrote:
> Hi, very new with Xen so am learning as I go.
> 
> Have rebuilt binutils to enable i386pep and "ld -V" confirms as such.
> 
> I can build xen without error but how should I be passing in the EFI_Vendor
> parameter?  I'm currently having to cp the xen-4.2.2.efi from
> /usr/lib64/efi/ into my /boot/efi/EFI/ubuntu dir.
> 
> (Expecting that my EFI_VENDOR parameter should be "EFI/ubuntu".)

Yes. You'd set EFI_VENDOR in root's environment, or pass the value
on the "make install-xen" command line.

> Have created a xen-4.2.2.cfg file in /boot/efi/EFI/ubuntu right next to the
> .efi.  Boot shows its using the .cfg file but I get an error about no Dom0
> Kernel could be found.  I'm struggling to find or maybe understand the
> documentation/posts on this.  My xen-4.2.2.cfg is as follows...
> 
> [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
> 
> I've cp the kernel and ramdisk files into the same location as the
> .efi.  Please can someone point me at the right words to
> research/advise where I'm going wrong.  Any help apprecaited.

Are you sure about this being in the right place? What exact error
message are you getting?

Jan

Re: Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2

[Kristian Hagsted Rasmussen]

> -----Original Message-----
> From: xen-devel-bounces@lists.xen.org [mailto:xen-devel-
> bounces@lists.xen.org] On Behalf Of Jan Beulich
> Sent: 15. juli 2013 09:09
> To: Kelvin Middleton
> Cc: xen-devel@lists.xenproject.org
> Subject: Re: [Xen-devel] Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2
> 
> >>> On 13.07.13 at 16:59, Kelvin Middleton <kelvin.middleton@gmail.com>
> wrote:
> > Hi, very new with Xen so am learning as I go.
> >

> > Have created a xen-4.2.2.cfg file in /boot/efi/EFI/ubuntu right next
> > to the .efi.  Boot shows its using the .cfg file but I get an error
> > about no Dom0 Kernel could be found.  I'm struggling to find or maybe
> > understand the documentation/posts on this.  My xen-4.2.2.cfg is as
> follows...
> >
> > [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

I am not completely sure if it is necessary to rename the linux kernel to end on .efi,
I have always done this as it is necessary for booting linux directly from efistub.
However when renaming the linux kernel vmlinuz*.efi and placing it in the same
folder as the xen.efi, I can boot from efi without problems.
It must be said that I have compile my on kernel with CONFIG_EFI_STUB=y.

/Kristian

Re: Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2

[Jan Beulich]

>>> On 15.07.13 at 09:48, Kristian Hagsted Rasmussen <kristian@hagsted.dk> 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
> 
> I am not completely sure if it is necessary to rename the linux kernel to 
> end on .efi,

Whatever the filename following the kernel= above. I.e. if you
name it *.efi, then the line above also would need to be changed.

> It must be said that I have compile my on kernel with CONFIG_EFI_STUB=y.

The code this enables should remain unused when running under
Xen.

Jan

Re: Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2

[Kristian Hagsted Rasmussen]

> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: 15. juli 2013 10:03
> To: Kelvin Middleton; Kristian Hagsted Rasmussen
> Cc: xen-devel@lists.xenproject.org
> 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@hagsted.dk>
> 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
> >
> > I am not completely sure if it is necessary to rename the linux kernel
> > to end on .efi,
> 
> Whatever the filename following the kernel= above. I.e. if you name it *.efi,
> then the line above also would need to be changed.

I forgot to mention that I also rename the file in the kernel= line.
But I guess this renaming to *.efi is not necessary as it is not calling the stub part
of the kernel.

> 
> > It must be said that I have compile my on kernel with CONFIG_EFI_STUB=y.
> 
> The code this enables should remain unused when running under Xen.
> 
> Jan

Re: Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2

[Jan Beulich]

>>> On 15.07.13 at 11:10, Kristian Hagsted Rasmussen <kristian@hagsted.dk> wrote:
>> From: Jan Beulich [mailto:JBeulich@suse.com]
>> Sent: 15. juli 2013 10:03
>> To: Kelvin Middleton; Kristian Hagsted Rasmussen
>> Cc: xen-devel@lists.xenproject.org 
>> 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@hagsted.dk>
>> 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
>> >
>> > I am not completely sure if it is necessary to rename the linux kernel
>> > to end on .efi,
>> 
>> Whatever the filename following the kernel= above. I.e. if you name it 
> *.efi,
>> then the line above also would need to be changed.
> 
> I forgot to mention that I also rename the file in the kernel= line.
> But I guess this renaming to *.efi is not necessary as it is not calling the 
> stub part of the kernel.

Correct.

Jan

Re: Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2

[Kristian Hagsted Rasmussen]

> -----Original Message-----
> From: xen-devel-bounces@lists.xen.org [mailto:xen-devel-
> bounces@lists.xen.org] On Behalf Of Jan Beulich
> Sent: 15. juli 2013 11:35
> To: Kelvin Middleton; Kristian Hagsted Rasmussen
> Cc: xen-devel@lists.xenproject.org
> 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@hagsted.dk>
> wrote:
> >> From: Jan Beulich [mailto:JBeulich@suse.com]
> >> Sent: 15. juli 2013 10:03
> >> To: Kelvin Middleton; Kristian Hagsted Rasmussen
> >> Cc: xen-devel@lists.xenproject.org
> >> 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@hagsted.dk>
> >> 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

Re: Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2

[Kelvin Middleton]

[-- Attachment #1.1: Type: text/plain, Size: 2293 bytes --]

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@hagsted.dk>wrote:

>
>
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xen.org [mailto:xen-devel-
> > bounces@lists.xen.org] On Behalf Of Jan Beulich
> > Sent: 15. juli 2013 11:35
> > To: Kelvin Middleton; Kristian Hagsted Rasmussen
> > Cc: xen-devel@lists.xenproject.org
> > 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@hagsted.dk>
> > wrote:
> > >> From: Jan Beulich [mailto:JBeulich@suse.com]
> > >> Sent: 15. juli 2013 10:03
> > >> To: Kelvin Middleton; Kristian Hagsted Rasmussen
> > >> Cc: xen-devel@lists.xenproject.org
> > >> 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@hagsted.dk>
> > >> 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
>

[-- Attachment #1.2: Type: text/html, Size: 3850 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2

[Jan Beulich]

>>> On 15.07.13 at 22:37, Kelvin Middleton <kelvin.middleton@gmail.com> wrote:
> 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 
> ??

Floating Point Unit. This is a problem we've seen elsewhere already,
and is - afaict - a clear violation of the EFI specification by your
system's EFI implementation: Runtime services functions are not
permitted to use floating point registers. Please contact the machine
or BIOS vendor for an update; I don't see us trying to work around
such fundamental flaws.

Jan

Re: Building Xen 4.2.2 w/EFI on Ubuntu Server 12.04.2

[Eric Shelton]

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@gmail.com>
> To: Kristian Hagsted Rasmussen <kristian@hagsted.dk>
> Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
>         Jan Beulich <JBeulich@suse.com>
> 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@hagsted.dk>wrote:
>
> >
> >
> > > -----Original Message-----
> > > From: xen-devel-bounces@lists.xen.org [mailto:xen-devel-
> > > bounces@lists.xen.org] On Behalf Of Jan Beulich
> > > Sent: 15. juli 2013 11:35
> > > To: Kelvin Middleton; Kristian Hagsted Rasmussen
> > > Cc: xen-devel@lists.xenproject.org
> > > 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@hagsted.dk>
> > > wrote:
> > > >> From: Jan Beulich [mailto:JBeulich@suse.com]
> > > >> Sent: 15. juli 2013 10:03
> > > >> To: Kelvin Middleton; Kristian Hagsted Rasmussen
> > > >> Cc: xen-devel@lists.xenproject.org
> > > >> 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@hagsted.dk>
> > > >> 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
> >