3:17 p.m.
Adam,
I am forwarding this discussion to kexec list. Right now, I don't have time
to try it. I am hoping somebody on the list will have enthusiasm to
give kdump on on live images a try and see what are the issues.
Thanks
Vivek
On Thu, Jul 25, 2013 at 09:13:14AM -0700, Adam Williamson wrote:
Hi, dedo. I realized I forgot to pass this onto you. I forwarded
your
concerns about kdump on live images to our kdump person (hi Vivek!), he
had some comments - see attached. Vivek, what is it you'd like dedo or
me to 'play with'?
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
Date: Fri, 12 Jul 2013 11:55:59 -0400
From: Vivek Goyal <vgoyal(a)redhat.com>
To: Adam Williamson <awilliam(a)redhat.com>
Subject: Re: F20 System Wide Change: Enable kdump on secureboot machines
User-Agent: Mutt/1.5.21 (2010-09-15)
Message-ID: <20130712155559.GF2272(a)redhat.com>
On Fri, Jul 12, 2013 at 08:29:21AM -0700, Adam Williamson wrote:
> On Fri, 2013-07-12 at 10:55 -0400, Vivek Goyal wrote:
> > On Thu, Jul 11, 2013 at 02:09:54PM -0700, Adam Williamson wrote:
> > > On Thu, 2013-07-11 at 14:13 -0400, Vivek Goyal wrote:
> > >
> > > > I think this is a wrong impression. Kdump should work in Fedora. For
a
> > > > long time I got the feedback that fedora users don't care about
kdump
> > > > working. But I think kdump is an important debugging facility and is
> > > > very useful for enterprise distro. So at times it should be useful
for
> > > > fedora users too.
> > > >
> > > > So now I am trying to make sure things work well in Fedora.
> > >
> > > FWIW, dedoimedo (a notoriously tough distro reviewer) mentioned to me in
> > > private correspondence that he's been hitting a kernel crash with F19
> > > with one of his test systems and he'd want to use kdump to try and
> > > diagnose it, only it doesn't work on live images, he says. Is that
> > > accurate? If so, can it be made to work on live images?
> >
> > I have never tested kdump on live images. What's the problem he is facing?
>
> Taking off list since it's a bit OT, here's what I got from him:
>
> "I was not able to install the server because of this. I also don't have
> a kdump core, cause it's not enable in the live session."
Ok, I think he might be facing multiple issues here.
- kexec-tools rpm is not available in live media.
- crashkernel=128M is not enabled on kernel command line.
I suspect it could be rpm thing.
>
> "P.S. I would recommend setting up live beta editions with kdump enabled
> and ask user just to configure the dump storage, because this can allow
> you to collect cores and sort them out."
>
> "... the best thing would be to configure kdump really.
> Have the crash offset configured,
Not sure what he means by crash core offset configured. Most likely he
is referring to crashkernel= parameter which needs to be specified on
kernel command line. That one can do by editing grub command line
when live media boots.
> just leave the last stage for
> destination. That would be useful, maybe for v20."
Will you be interested in playing with it a bit.
Thanks
Vivek