I wrote to this list as it appears that there were some folks with similar problems few months ago.
Okay then, the bisect message will be on edk2 list when it's done.
Blank Field <ihatethisfield > writes:
> Updated to fc24, got unbootable 4.5.0-rc7 kernel, qemu 2.5.0 and
> The problem still persists. I was able to jump into ovmf setup menu,
> the drive is recognised. Trying booting from any partition results in
> a hang and errors.
> First it says about invalid MBR on a GPT disk, the last two lines of
> the debug console are:
> ExtractConfig: BlockToConfig(): Invalid Parameter, Progress="<null
> TmpRequest != ((void *) 0)
> In short, updating to qemu 2.5 did not help.
The first problem ("invalid MBR on a GPT disk") should be bisectable.
Can you please bisect it?
The second problem (the failed ASSERT) is an incompatibility between
edk2 and iPXE. I will report that issue to the respective edk2 and iPXE
maintainers, and attempt to work it around in OVMF. Until then, you can
suppress it by setting <rom bar='off'/> in your domain XML
(<http://libvirt.org/formatdomain.html>), under the NIC's XML element.
In the future, please report edk2 issues to the edk2-devel list as well.
(NOTE: you have to subscribe in order to post. See
<https://lists.01.org/mailman/listinfo/edk2-devel>.) You can't expect me
to browse this list for bugs I might feel like fixing -- bugs that
aren't even specific to the OVMF platform in edk2. You can also report
edk2 problems under <https://github.com/tianocore/edk2/issues/>, but be
advised that (a) that tracker is also for all of edk2, not just OVMF,
(b) the edk2 maintainers follow the list much more closely than the
github issue tracker.
vfio-users mailing list
vfio-users redhat com