Re: [Xen-users] status of guest/DomU UEFI + Grub support in Xen 4.6.1?

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Tue, Feb 23, 2016 at 08:04:52AM -0800, suse.dev@xxxxxx wrote:
> On 02/23/2016 07:34 AM, Roger Pau Monné wrote:
> > Those are not partitions, those are actual disks. Have you tried to make
> > xvda the disk that contains the UEFI partition, so that OVMF can find it?
> >
> > It's just a wild guess, since I've never used OVMF myself.
> 
> I swtiched to
> 
>  disk = [ 'phy:/dev/VG0/tEFI,xvda,w',
>           'phy:/dev/VG0/tBOOT,xvde,w',
>           'phy:/dev/VG0/tSWAP,xvdf,w',
>           'phy:/dev/VG0/tROOT,xvdg,w',
>         ]
> 
> where via parted
> 
>  select /dev/xvda
>  mklabel gpt
>  mkpart ESP fat32 1MiB 100%
>  set 1 boot on
> 
> as well as systemd-boot as bootloader.  It seems far less bloated/opaque than 
> Grub for DomU use.
> 
> Repeating the install process, logged into the being-installed-Guest's chroot,
> 
>  cat /boot/efi/loader/loader.conf
>   default  arch
>   timeout  4
>   editor   0
> 
>  cat << EOF > /boot/efi/loader/entries/arch.conf
>   title          Arch
>   linux          /vmlinuz-linux
>   initrd         /initramfs-linux.img
>   options        root=LABEL=ROOT resume=LABEL=SWAP rw
> 
>  mkinitcpio -p linux
>       ...
>       ==> Image generation successful
>  bootctl --path=/boot/efi install
>       Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to 
> "/boot/efi/EFI/systemd/systemd-bootx64.efi".
>       Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to 
> "/boot/efi/EFI/Boot/BOOTX64.EFI".
>       Not booted with EFI, skipping EFI variable setup.
> 
> then stop/start the DomU
> 
>  xl create ./arch.cfg
>       Parsing config from ./arch.cfg
>       got a tsc mode string: "default"
>  xl list
>       Name                                        ID   Mem VCPUs      State   
> Time(s)
>       Domain-0                                     0  4096     1     r-----   
>  1798.4
>       arch                                        70  2048     1     -b----   
>     1.2
> 
> but, as before, same iPXE-boot cruft ...
> 
> >> Is is at all functional? supported? recommended?
> >

Do you have bios='ovmf' in your guest config file? It seems that the
guest is booting with legacy bios (seabios).

Furthermore nvram isn't supported at the moment, so your modification will be
lost. What we do in our test system is to place grubx64 efi into a known
location so that it always gets picked up by OVMF.

If you don't require any specific functionality provided by UEFI, it's
better to just use legacy bios. OVMF needs more work to make it work out
of the box.

Wei.

> > Adding Wei and Anthony who have worked with OVMF and Xen.
> 
> Thanks.
> 
> _______________________________________________
> 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