>> Your NvVars file could be very old, maybe a remnant of your earlier
> Will check the date, but i doubt about this. Maybe there was no problem at
> all and i just need to create a normal BootOrder entry.
Oct 9 2015. Old. Okay.
> Separate VARS...
<os>
<type arch='x86_64' machine='pc-i440fx-2.4'>hvm</type>
<loader readonly='yes'
type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/vm1_VARS.fd</nvram>
<boot dev='hd'/>
<bootmenu enable='yes'/>
</os>
Seems separate enough for me.
Booting the bootmgfw.efi which is located into
/boot/efi/microsoft/boot/, apparently actually loads something of
little use. All i see now is a black screen with a "_" on it and some
CPU/disk activity. I guess the guest OS boots, but there are
display-related problems. Out of scope. Thanks for clarification, the
problem wasn't existent and the end-user wasn't smart enough.
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
