Hello Michal,
Hello Stefano,
Thanks Michal. Your receipt worked.
Regards,
Oleg Nikitenko
вт, 3 окт. 2023 г. в 10:33, Michal Orzel :
>
>
> On 03/10/2023 09:28, Michal Orzel wrote:
> >
> >
> > Hi Oleg, Stefano
> >
> > On 03/10/2023 02:13, Stefano Stabellini wrote:
> >> Hi Oleg,
> >>
> >> You are
On 03/10/2023 09:28, Michal Orzel wrote:
>
>
> Hi Oleg, Stefano
>
> On 03/10/2023 02:13, Stefano Stabellini wrote:
>> Hi Oleg,
>>
>> You are getting this output:
>>
>>> (XEN) d0v0 Forwarding AES operation: 3254779951 136bb000 ->
>>> f000
>>
>> Which means that the guest p
Hi Oleg, Stefano
On 03/10/2023 02:13, Stefano Stabellini wrote:
> Hi Oleg,
>
> You are getting this output:
>
>> (XEN) d0v0 Forwarding AES operation: 3254779951 136bb000 ->
>> f000
>
> Which means that the guest physical address is 0x136bb000 and
> the translated ph
Hi Oleg,
You are getting this output:
> (XEN) d0v0 Forwarding AES operation: 3254779951 136bb000 ->
> f000
Which means that the guest physical address is 0x136bb000 and
the translated physical address is 0xf000. It generates an
error so you are asking if
Hello Stefano,
Hello Julien,
> OK I see the question is about the Xilinx Xen tree. In the logs below we
have:
I see. After the correction r2 to r1 CSU got aborted immediately.
(XEN) d0v0 Forwarding AES operation: 3254779951 136bb000 ->
f000
Received exception
MSR: 0x200, EAR:
