[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] [Help] Xen-4.2.2 EFI Config File



On Sun, 2013-07-14 at 10:28 +0100, Kelvin Middleton wrote:
> Hi, I'm struggling to write a correct xen-4.2.2.cfg file to accompany
> my xen-4.2.2.efi to boot my Ubuntu Server 12.04.2 as Dom0.
> 
> 
> Built Xen from source, put the built .efi file into the same dir as my
> grub EFI file, created a .cfg file and put it in the same location.
> 
> 
> Boot works, EFI says its using the configuration file and then errors
> say No Dom0 kernel image specified.

A total wild guess but perhaps a full path (relative to the EFI
partition) is required? Not sure if you will want Linux style / path
separators or Windows/EFI \ ones, or even if you might need to escape
them as \\ (probably not).

I assume vmlinuz-3.5.0-36-generic does actually exist somewhere in the
EFI partition?

I guess grub.efi works -- what paths does it use?

Ian.

> 
> Partitions:
> 500MB - EFI Partition
> 500MB - /boot
> 60GB - LVM
> --15GB VG0-Dom0
> --4GB VG0-Dom0_swap
> --41GB spare
> 
> 
> /boot/efi/EFI/ubuntu contains the Ubuntu grub .efi installed by
> default.  Also contains my xen-4.2.2.efi and .cfg.
> 
> 
> Where should I be placing the Dom0 kernel image and initrd files?
>  I've currently put them into the same location as the .efi?
> 
> 
> xen-4.2.2.cfg looks like...
> 
> 
> [global]
> default=xen
> 
> 
> 
> 
> [xen]
> options=console=vga dom0_mem=1024M,max=1024M dom0_max_vcpus=1
> loglvl=all noreboot
> kernel=vmlinuz-3.5.0-36-generic root=/dev/mapper/VG0-Dom0
> ramdisk=initrd.img-3.5.0-36-generic
> *******************End of file***************************
> 
> 
> Any help appreciated.
> 
> 
> Thanks,
> 
> 
> Kelvin
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.