Re: [Xen-devel] [edk2] OVMF broken under Xen (in PCI initialisation)

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

> I tried to make RootBridgeIoConfiguration() return EFI_UNSUPPORTED
> (see the attachment), and those asserts were gone. However, the system
> stuck somewhere after loading shell.efi. Here are the messages from the
> debug log:
>
> BdsLibConnectAll
> Select Item: 0xE
> Memory  Previous  Current    Next
>  Type    Pages     Pages     Pages
> ======  ========  ========  ========
>   0A    00000004  00000001  00000004
>   09    00000008  00000011  00000015
>   00    00000004  00000001  00000004
>   06    00000024  00000057  0000006C
>   05    00000030  00000063  0000007B
>   03    00000180  0000048D  000005B0
>   04    00000F00  00000B65  00000F00
> Booting EFI Internal Shell
> InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3EA580C0
> Loading driver at 0x0003E03F000 EntryPoint=0x0003E03F240 Shell.efi
> InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3EA58B98
> InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 3EA54320
> InstallProtocolInterface: 752F3136-4E16-4FDC-A22A-E5F46812F4CA 3EA53CD8
> InstallProtocolInterface: 6302D008-7F9B-4F30-87AC-60C9FEF5DA4E 3E16B580
>
> I couldn't find out where it stuck unless there is a way to attach gdb
> to Xen HVM for source level debugging :-(

You can use gdbsx (from tools/debugger/gdbsx in the Xen tree) which acts
like gdbserver.  (It is very rough around the edges, but does function.)

~Andrew


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