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

=?gb18030?b?u9i4tKO6IFtYZW4gQVJNNjRdIFNhdmUgY29yZWR1?==?gb18030?b?bXAgbG9nIHdoZW4geGVuL2RvbTAgY3Jhc2ggb24g?==?gb18030?b?QVJNNjQ/?=


  • To: "=?gb18030?b?SnVsaWVuIEdyYWxs?=" <julien@xxxxxxx>, "=?gb18030?b?eGVuLWRldmVs?=" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: "=?gb18030?b?amluY2hlbg==?=" <jinchen1227@xxxxxx>
  • Date: Fri, 3 Jul 2020 14:02:43 +0800
  • Delivery-date: Fri, 03 Jul 2020 06:03:10 +0000
  • Feedback-id: webmail:qq.com:bgforeign:bgforeign11
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

Thank you for your reply!

On 02/07/2020 02:41, jinchen wrote:
>> Hello xen experts:
>>
>> Is there any way to save xen and dom0 core dump log when xen or dom0
>> crash on ARM64 platform?

>Usually all the crash stack trace (Xen and Dom0) should be output on the
>Xen Console.

But if I don't connect a debug serial and want to check the dump error after reboot?

>>      I find that the kdump seems can't run on ARM64 platform?

>We don't have support for kdump/kexec on Arm in Xen yet.

I find the kdump seems the appropriate way to do this, but it doesn't support xen arm64.

>>      Are there any patches or other way to achive this goal?

>I am not aware of any patches, but they would be welcomed.

>For other way, it depends what exactly you expect. Do you need more than
>the stack trace?

The stack trace will be ok, if other infomantion can be save will be better (like memory/vcpu/domain, etc.)




 


Rackspace

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