[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] strange behavior with Multiboot2 on EFI

Is there some way to easily print stack dump with QEMU? Adding -d
guest_errors prints only register state.

2018-06-14 13:24 GMT+03:00 Jan Beulich <JBeulich@xxxxxxxx>:
>>>> On 14.06.18 at 12:11, <kristaps.civkulis@xxxxxxxxx> wrote:
>>>  As you should have a xen.efi available from that same build, could
>>> you try running that (from the EFI shell) instead? Sadly there's no way
>>> to bypass the call in the multiboot2 case, while with xen.efi you could
>>> pass "/basevideo" to prevent the call from being made.
>> When I launched QEMU I pressed ESC to get into UEFI menu.
>> While in UEFI menu I did:
>> Boot Maintainance Manager -> Boot Options -> Add Boot Option -> chose
>> xen.efi file and in Input Optional Data I added /basevideo . Saved
>> changes and then booted this new entry.
>> After few seconds QEMU crashed with following output:
>> qemu: fatal: Trying to execute code outside RAM or ROM at 0x00000000000b0000
>> RAX=0000000000000000 RBX=000000007e622418 RCX=0000000000000000
>> RDX=000000007ff09320
>> RSI=000000007d86e368 RDI=000000007e622418 RBP=000000007ff09370
>> RSP=000000007ff092c8
>> R8 =000000007ff276bf R9 =000000007e623298 R10=0000000000000011
>> R11=0000000000000000
>> R12=0000000000000001 R13=00000000003da367 R14=0000000000000009
>> R15=0000000000000000
>> RIP=00000000000affb8 RFL=00000246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> RIP is clearly fishy, but without any dump of the stack one can't even guess
> how execution made it there.
> Jan

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.