>>> On 30.10.12 at 18:03, Olaf Hering wrote:
> On Tue, Oct 30, Jan Beulich wrote:
>
>> And iirc you're doing this relocation because otherwise the newly
>> booting kernel image may get overwritten at an (from its
>> perspective) arbitrary location. What I'm trying to point out is
>> that the shar
On Tue, Oct 30, Jan Beulich wrote:
> And iirc you're doing this relocation because otherwise the newly
> booting kernel image may get overwritten at an (from its
> perspective) arbitrary location. What I'm trying to point out is
> that the shared info structure is not the only thing (potentially)
>>> On 30.10.12 at 17:30, Olaf Hering wrote:
> On Tue, Oct 30, Jan Beulich wrote:
>
>> >>> On 30.10.12 at 16:47, Olaf Hering wrote:
>> > This is a respin of 00e37bdb0113a98408de42db85be002f21dbffd3
>> > ("xen PVonHVM: move shared_info to MMIO before kexec").
>> >
>> > Currently kexec in a PVonH
On Tue, Oct 30, Jan Beulich wrote:
> >>> On 30.10.12 at 16:47, Olaf Hering wrote:
> > This is a respin of 00e37bdb0113a98408de42db85be002f21dbffd3
> > ("xen PVonHVM: move shared_info to MMIO before kexec").
> >
> > Currently kexec in a PVonHVM guest fails with a triple fault because the
> > new
>>> On 30.10.12 at 16:47, Olaf Hering wrote:
> This is a respin of 00e37bdb0113a98408de42db85be002f21dbffd3
> ("xen PVonHVM: move shared_info to MMIO before kexec").
>
> Currently kexec in a PVonHVM guest fails with a triple fault because the
> new kernel overwrites the shared info page. The exac
This is a respin of 00e37bdb0113a98408de42db85be002f21dbffd3
("xen PVonHVM: move shared_info to MMIO before kexec").
Currently kexec in a PVonHVM guest fails with a triple fault because the
new kernel overwrites the shared info page. The exact failure depends on
the size of the kernel image. This
6 matches
Mail list logo
