From: Stefan Berger <stefanb@linux.ibm.com>
To: The development of GNU GRUB <grub-devel@gnu.org>,
Mate Kukri <mate.kukri@canonical.com>
Cc: Daniel Kiper <dkiper@net-space.pl>
Subject: Re: OpenStack boot regressions caused by "ppc64: Restrict memory allocations for kernel and initrd"
Date: Wed, 14 Feb 2024 10:05:23 -0500 [thread overview]
Message-ID: <4910224b-81e4-4ca8-8ae1-0c0c1a0d63e1@linux.ibm.com> (raw)
In-Reply-To: <CAAfJHtruj=C2YK3+tfz=no8agesS-qr1vyFND7G47Uof_zY6aQ@mail.gmail.com>
On 2/14/24 09:31, Mate Kukri wrote:
> Hello,
>
> We have discovered a boot regression on virtual machines in
> Canonical's OpenStack cloud when upgrading from 2.12-rc1 to 2.12 on
> ppc64.
>
> It was tracked down to the following patchset:
> https://lists.gnu.org/archive/html/grub-devel/2023-11/msg00188.html
>
> The boot regressions seem to be related to GRUB running out of memory
> when loading initrds:
> https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/ppc64el/z/zsys/20240213_214024_bf6af@/log.gz
>
> As a temporary solution, I have reverted the patchset in Ubuntu, but I
> wonder if anything else is effected by this.
I don't think it's a solution to revert this change since grub is not
supposed to use the memory described in the cover letter. Can you try to
give more memory to a VM? How much memory do the VMs have? What
hypervisor is this, KVM or PowerVM?
>
> Mate Kukri
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
prev parent reply other threads:[~2024-02-14 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 14:31 OpenStack boot regressions caused by "ppc64: Restrict memory allocations for kernel and initrd" Mate Kukri
2024-02-14 15:05 ` Stefan Berger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4910224b-81e4-4ca8-8ae1-0c0c1a0d63e1@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=mate.kukri@canonical.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).