On Fri, 26 Apr 2024 at 16:48, Julian Andres Klode <
julian.kl...@canonical.com> wrote:
> On Thu, Apr 25, 2024 at 09:10:08PM +0100, Alex Bennée wrote:
> > Alex Bennée writes:
> >
> > > Julian Andres Klode writes:
> > >
> > >> On Thu,
Alex Bennée writes:
> Julian Andres Klode writes:
>
>> On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote:
>>>
>>> Continuing to debug on QEMU it seems there is an incompatibility with
>>> the images and the peloader (which overrides the norm
Julian Andres Klode writes:
> On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote:
>>
>> Continuing to debug on QEMU it seems there is an incompatibility with
>> the images and the peloader (which overrides the normal efi loader):
>>
>&
62a000 in ?? ()
#30 0xafafafaf6c617470 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Is it possible to override the peloader or does the Xen image need to be
prepared a certain way?
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
en using the same grub.cfg and get most of the way through the
Dom0 boot before that failed for unrelated issues. So it seems there is
a bug introduced by the debian customisation of the package or missing a
fix from the current state of upstream.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
--
Alex Bennée
Emulation and Virtualisation Tech Lead @ Linaro
/systemd/system)
LSM: AppArmor: enabled
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
I can confirm I've seen the same symptoms on my system. I was unable to
get a working X session (although the cursor would appear on one of my
two displays). Manual startx would also fail.
HW:
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
(rev 06)
8 matches
Mail list logo
