The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: grub (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in
I'd just like to report in that I couldn't get it to work, it only did
after raising the limit to 256M on a server with 256GB of memory.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
** No longer affects: grub (Ubuntu Raring)
** No longer affects: grub (Ubuntu Quantal)
** No longer affects: grub (Ubuntu Saucy)
** Changed in: grub (Ubuntu Precise)
Assignee: Chris J Arges (arges) = (unassigned)
** Changed in: grub (Ubuntu Precise)
Status: In Progress = Confirmed
Please keep in mind the 128Mb is some kind of catchall for defined when
memory sizes did not go much higher than 16Gb. I will inquire in the ML
that covers makedumpfile to see if there is a way to come up with an
estimate of the required memory and will report back.
In the meantime, I don't see
RFE
Let there be a separate tool/command that would provide an estimate of
the memory required for the localhost.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/785394
Title:
Bryan: Are you saying 256MB was needed in order for the crash kernel to
boot, that 128MB was not enough?
(I'm not sure that there is any advantage to reserving more memory than
needed, aside from the kernel one day growing to need 129MB)
--
You received this bug notification because you are a
128MB didn't work
256MB did
Nothing else was tested on this machine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/785394
Title:
Hard-coded crashkernel=... memory reservation in
Ah, okay, that's an issue. Not only do we not have an easy way of
measuring how much memory a kernel needs to boot, we don't know how that
requirement varies depending on the system configuration...
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Also affects: kexec-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kexec-tools (Ubuntu)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: kexec-tools (Ubuntu)
Importance: Undecided = Medium
** Changed in: kexec-tools (Ubuntu)
Status: New
Pushed changes into kexec-tools trusty. Let's test these changes first,
then modify the grub packages in earlier releases via SRU if trusty is
working fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
** Branch linked: lp:ubuntu/trusty-proposed/kexec-tools
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/785394
Title:
Hard-coded crashkernel=... memory reservation in
This bug was fixed in the package kexec-tools - 1:2.0.3-4ubuntu3
---
kexec-tools (1:2.0.3-4ubuntu3) trusty; urgency=low
* Increase memory parameter crashkernel command line to 128M to avoid
OOM kernel panic. (LP: #785394)
-- Chris J Arges chris.j.ar...@ubuntu.com Wed, 18 Dec
** Also affects: grub2 (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: kexec-tools (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: kexec-tools (Ubuntu
** Also affects: grub (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: kexec-tools (Ubuntu)
** No longer affects: kexec-tools (Ubuntu Precise)
** No longer affects: kexec-tools (Ubuntu Quantal)
** No longer affects: kexec-tools (Ubuntu Raring)
** No longer affects:
I systematically change the setting on all my VMs to 128M as I have had
repeated failure with 64M. I think that the default should be raised to
128Mb which is the default on Debian anyway.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Agreed. It's not clear that there is *any* standard Ubuntu kernel
configuration that can boot in 64MB. And having that as a default is
worse than useless, because the crash-kernel's OOM prevents the system
from recovering automatically after a kernel crash.
--
You received this bug notification
@Daniel
I'm wrong, not fixed in 13.04+
I ran some tests:
@Chiluk first up vm images do only need 64 mb reserved:
Trusty 512 MB (m1.tiny) image on OpenStack: allocted 64 MB of ram for
crashdump and it worked. (dump size of 23 mb)
Desktop images fail
Trusty 2047 MB (Vagrant/Virtualbox desktop
Bryan: Could you elaborate on how this issue appears to be fixed in
13.04? Was the memory reservation increased to 128MB, or is the kernel
now capable of booting in 64MB? Given the lack of any updates here, I'm
doubtful that any progress has been made at all.
Dave: Have you tried crash-booting a
This appears to be fixed in 13.04+. Any chance we can get a fix
backported to 12.04?
If not, can we increase the memory by default?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
19 matches
Mail list logo
