Thanks very much for the help!
Unfortunately I did try that previously and was still dumped into the efi shell.
Looking round again, I didn't build my OVMF with secure boot enabled. Going to see if I get any joy rebuilding with secure boot support.
thanks againUnfortunately I did try that previously and was still dumped into the efi shell.
Looking round again, I didn't build my OVMF with secure boot enabled. Going to see if I get any joy rebuilding with secure boot support.
On Tue, Mar 22, 2016 at 3:35 AM, Andrea Bolognani <abologna@xxxxxxxxxx> wrote:
On Mon, 2016-03-21 at 13:53 -0500, jsl6uy js16uy wrote:
> for this host....my nvram setting look like
> <os>
> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type>
> <loader readonly='yes' type='pflash'>/home/xyz/OVMF.fd</loader>
> <nvram template='/usr/share/OVMF/OVMF_VARS.fd'>/var/lib/libvirt/qemu/nvram/X_VARS.fd</nvram>
> <boot dev='hd'/>
> </os>
Have you tried deleting the *VARS.fd in /var/lib/libvirt/qemu/nvram
and changing the 'template' attribute so that it points to the
*VARS.fd file you should have in your edk2 source tree, eg. the one
matching the OVMF.fd you're using to boot?
Not sure if that would help, but it's definitely worth a shot :)
Cheers.
--
Andrea Bolognani
Software Engineer - Virtualization Team
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
