9f8c9 which includes commit
>>> 3b5de119f0399cbe745502cb6ebd5e6633cc139c "86/msr: fix handling of
>>> MSR_IA32_PERF_{STATUS/CTL}". I think this should address this error
>>> recorded in xen's dmesg:
>>>
>>> (XEN) d11v0 VIRIDIAN CRASH: 3b c096 75b12c5 9e7f1580 0
>>
502cb6ebd5e6633cc139c "86/msr: fix handling of
> > MSR_IA32_PERF_{STATUS/CTL}". I think this should address this error
> > recorded in xen's dmesg:
> >
> > (XEN) d11v0 VIRIDIAN CRASH: 3b c096 75b12c5 9e7f1580 0
>
> It seems to me that you impl
> -Original Message-
> From: Jan Beulich
> Sent: 03 February 2021 15:43
> To: p...@xen.org
> Cc: xen-devel@lists.xenproject.org; 'James Dingwall'
>
> Subject: Re: VIRIDIAN CRASH: 3b c096 75b12c5 9e7f1580 0
>
> On 03.02.2021 16:04, Paul Durrant w
On 03.02.2021 16:04, Paul Durrant wrote:
>> From: Xen-devel On Behalf Of Jan
>> Beulich
>> Sent: 03 February 2021 14:55
>>
>> On 01.02.2021 16:26, James Dingwall wrote:
>>> 21244@1612191983.282480:xen_platform_log xen platform: XEN|BUGCHECK:
>>> EXCEPTION (A824848948C2):
>>> 21244@1612191983
> -Original Message-
> From: Xen-devel On Behalf Of Jan
> Beulich
> Sent: 03 February 2021 14:55
> To: James Dingwall
> Cc: xen-devel@lists.xenproject.org
> Subject: Re: VIRIDIAN CRASH: 3b c0000096 75b12c5 9e7f1580 0
>
> On 01.02.2021 16:26, James Dingwall w
uld address this error
> recorded in xen's dmesg:
>
> (XEN) d11v0 VIRIDIAN CRASH: 3b c096 75b12c5 9e7f1580 0
It seems to me that you imply some information here which might
better be spelled out. As it stands I do not see the immediate
connection between the cit
VIRIDIAN CRASH: 3b c096 75b12c5 9e7f1580 0
I have removed `viridian = [..]` from the xen config nut still get this
reliably when launching PassMark Performance Test and it is collecting
CPU information.
This is recorded in the domain qemu-dm log:
21244@1612191983.279616:xen_platform_log xe
