On Fri, Mar 17, 2023 at 12:23 PM HAGIO KAZUHITO(萩尾 一仁) <k-hagio-ab@xxxxxxx> wrote:
On 2023/03/17 12:54, lijiang wrote:
> On Wed, Mar 15, 2023 at 7:19 PM <crash-utility-request@xxxxxxxxxx> wrote:
>
>> Date: Wed, 15 Mar 2023 12:18:47 +0100
>> From: Juergen Gross <jgross@xxxxxxxx>
>> To: crash-utility@xxxxxxxxxx
>> Cc: Juergen Gross <jgross@xxxxxxxx>
>> Subject: [PATCH v2 0/3] xen: several fixes for newer
>> Xen versions
>> Message-ID: <20230315111850.21395-1-jgross@xxxxxxxx>
>> Content-Type: text/plain; charset="US-ASCII"; x-default=true
>>
>> When trying to look into a vmcore in Xen mode which was obtained from
>> a machine running Xen 4.16, I realized that crash wasn't able to handle
>> that.
>>
>> Looking into the issue I found that crash is lacking several adaptions
>> to newer Xen versions (at least 4.13 onwards).
>>
>> There might be more missing, but it is now at least possible to do
>> _some_ debugging.
>>
>> Changes in V2:
>> - addressed comments
>>
>>
> Thank you for the update, Juergen.
>
> For the v2: Ack(with the warning fix).
Applied with the fix.
https://github.com/crash-utility/crash/commits/master
Thanks, Kazu.
(currently crash-utility@xxxxxxxxxx is not working?)
I saw a network maintenance notification, let's wait for a while.
Thanks.
Lianbo
-- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/crash-utility Contribution Guidelines: https://github.com/crash-utility/crash/wiki
