DomU UEFI configuration

DomU UEFI configuration

[Marcos E. Matsunaga]

[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]

Hi Anthony,


I am trying to run a DomU guest using OVMF. I have built xen staging 
with --with-ovmf option. I am able to install a new guest but I am 
unable to boot it (see the attached image).

The xl.cfg file I am using:

name='test_uefi'
memory=16384
disk=['file:/home/IMAGES/FEDORA/FC25/Fedora-Server-dvd-x86_64-25-1.3.iso,hdc:cdrom,r','/Repo/VM/test_uefi/System_UEFI.qcow2,raw,hda,w']
#disk=['/Repo/VM/test_uefi/System_UEFI.qcow2,raw,hda,w']
vif=['mac=00:16:3e:ff:ee:01,bridge=xenbr0', 
'mac=00:16:3e:ff:00:01,bridge=xenbr2']
guest_os_type='default'
bios='ovmf'
serial='pty'
xen_platform_pci=0
device_model_version='qemu-xen'
builder='hvm'
on_poweroff='destroy'
boot='dc'
vnc=1
vnclisten='0.0.0.0:5'
stdvga=1
videoram=16
on_crash='restart'
on_reboot='restart'
vcpus=8
maxmem=16384

Konrad Wilk suggested me to use try adding:

device_model_args_hvm=["fw_cfg","file=./my_blob.bin"];

But that didn't work. I also tried something similar to how KVM uses:

device_model_args_hvm=['-drive','file=/Repo/VM/perf1_uefi/OVMF_VARS.fd,if=pflash,format=raw,unit=1'];

It also didn't work.

How do you specify the NVRAM image to store the boot order?

Thanks for your  help.

-- 

Regards,

Marcos Eduardo Matsunaga

Linux & Virtualization
Corp Architecture - Development

“The statements and opinions expressed here are my own and do not
necessarily represent those of Oracle Corporation.”


[-- Attachment #2: Tianocore-boot-failed.png --]
[-- Type: image/png, Size: 19992 bytes --]

[-- Attachment #3: Type: text/plain, Size: 127 bytes --]

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

Re: DomU UEFI configuration

[Anthony PERARD]

On Tue, Mar 14, 2017 at 02:06:09PM +0000, Marcos E. Matsunaga wrote:
> Hi Anthony,
> 
> 
> I am trying to run a DomU guest using OVMF. I have built xen staging with
> --with-ovmf option. I am able to install a new guest but I am unable to boot
> it (see the attached image).
> 
> The xl.cfg file I am using:
> 
> name='test_uefi'
> memory=16384
> disk=['file:/home/IMAGES/FEDORA/FC25/Fedora-Server-dvd-x86_64-25-1.3.iso,hdc:cdrom,r','/Repo/VM/test_uefi/System_UEFI.qcow2,raw,hda,w']
> #disk=['/Repo/VM/test_uefi/System_UEFI.qcow2,raw,hda,w']
> vif=['mac=00:16:3e:ff:ee:01,bridge=xenbr0',
> 'mac=00:16:3e:ff:00:01,bridge=xenbr2']
> guest_os_type='default'
> bios='ovmf'
> serial='pty'
> xen_platform_pci=0
> device_model_version='qemu-xen'
> builder='hvm'
> on_poweroff='destroy'
> boot='dc'
> vnc=1
> vnclisten='0.0.0.0:5'
> stdvga=1
> videoram=16
> on_crash='restart'
> on_reboot='restart'
> vcpus=8
> maxmem=16384
> 
> Konrad Wilk suggested me to use try adding:
> 
> device_model_args_hvm=["fw_cfg","file=./my_blob.bin"];

Those are not QEMU options, so that would not work. And I don't think
using -fw_cfg would work with xen (if the options exist) as we almost
don't use fw_cfg.

> But that didn't work. I also tried something similar to how KVM uses:
> 
> device_model_args_hvm=['-drive','file=/Repo/VM/perf1_uefi/OVMF_VARS.fd,if=pflash,format=raw,unit=1'];
> 
> It also didn't work.

:(. I never tried, I'm not sure if it can work. Compare to KVM, we put
OVMF.fd into RAM instead of a pflash device emulated by QEMU.

Maybe one would need to load OVMF_CODE.fd instead of OVMF.fd, and OVMF
could then use OVMF_VARS.fd, but I never tried.

> How do you specify the NVRAM image to store the boot order?

-- 
Anthony PERARD

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