> Like this? I can't reliably test that it fixes the problem - for some
> bizarre reason, I can now load kernels without this patch. But it
> looks right and I can load kernels with it, too.
Turns out there's a problem. qemu puts ACPI tables at the top of ram. We have
to be careful to avoid sto
On Wed, Mar 28, 2007 at 03:00:08PM +0100, Paul Brook wrote:
> On Wednesday 28 March 2007 03:21, Daniel Jacobowitz wrote:
> > On Wed, Mar 28, 2007 at 12:35:18AM +0100, Thiemo Seufer wrote:
> > > Right, a piggyback-style loader would likely fail in that case.
> >
> > Which is exactly the interesting
On Wednesday 28 March 2007 03:21, Daniel Jacobowitz wrote:
> On Wed, Mar 28, 2007 at 12:35:18AM +0100, Thiemo Seufer wrote:
> > Right, a piggyback-style loader would likely fail in that case.
>
> Which is exactly the interesting case for x86_64. So, since Paul's
> verified that grub and lilo just
On Wed, Mar 28, 2007 at 12:35:18AM +0100, Thiemo Seufer wrote:
> Right, a piggyback-style loader would likely fail in that case.
Which is exactly the interesting case for x86_64. So, since Paul's
verified that grub and lilo just put them far apart, maybe bumping up
the size is the right thing to
Paul Brook wrote:
> > > Note, that does not readily work - this is where we load the
> > > compressed kernel image and initrd, but what matters is the size it
> > > gets uncompressed to.
> >
> > I think what matters is the space taken by (uncompressed and loaded)
> > kernel ALLOC segments. Everythi
> > Note, that does not readily work - this is where we load the
> > compressed kernel image and initrd, but what matters is the size it
> > gets uncompressed to.
>
> I think what matters is the space taken by (uncompressed and loaded)
> kernel ALLOC segments. Everything above that should be ok to
Daniel Jacobowitz wrote:
> On Tue, Mar 27, 2007 at 08:16:40PM +0100, Thiemo Seufer wrote:
> > Gwenole Beauchesne wrote:
> > > Hi,
> > >
> > > The following patch increases max kernel size to 8 MB when qemu is
> > > invoked
> > > with -kernel and -initrd. Otherwise, x86_64 kernel panics when load
On Tue, Mar 27, 2007 at 08:16:40PM +0100, Thiemo Seufer wrote:
> Gwenole Beauchesne wrote:
> > Hi,
> >
> > The following patch increases max kernel size to 8 MB when qemu is invoked
> > with -kernel and -initrd. Otherwise, x86_64 kernel panics when loading the
> > initrd (e.g. /x86_64/isolinux/a
Gwenole Beauchesne wrote:
> Hi,
>
> The following patch increases max kernel size to 8 MB when qemu is invoked
> with -kernel and -initrd. Otherwise, x86_64 kernel panics when loading the
> initrd (e.g. /x86_64/isolinux/alt0/{vmlinuz,all.rdz}).
I would like a patch which adjusts the initrd load
On Tue, Mar 27, 2007 at 06:14:22PM +0200, Gwenole Beauchesne wrote:
> Hi,
>
> The following patch increases max kernel size to 8 MB when qemu is invoked
> with -kernel and -initrd. Otherwise, x86_64 kernel panics when loading the
> initrd (e.g. /x86_64/isolinux/alt0/{vmlinuz,all.rdz}).
When I t
Hi,
The following patch increases max kernel size to 8 MB when qemu is invoked
with -kernel and -initrd. Otherwise, x86_64 kernel panics when loading the
initrd (e.g. /x86_64/isolinux/alt0/{vmlinuz,all.rdz}).
Thanks,
Gwenole.
2007-03-27 Gwenole Beauchesne <[EMAIL PROTECTED]>
* hw/pc
11 matches
Mail list logo
