[RFC] [KDUMP] [PROPOSED WORK] kdump on Xen hypervisor and guests, more tests for utilities, like makedumpfile, mkdumprd, kexec etc
vgoyal at redhat.com
Tue Jun 24 08:42:43 EDT 2008
On Mon, Jun 23, 2008 at 07:42:50PM +0530, Subrata Modak wrote:
> Cai has proposed to work on the above LTP-KDUMP test cases
> enrichment/enhancements. Please let us know about your views on the
> same. We encourage people to review his proposal and the corresponding
> upcoming test cases. I am going to put this soon on the LTP-KDUMP plan
That's a very good idea. We need to increase kdump test coverage and
automate the whole thing.
> Here is my first draft plan of Kexec/Kdump tests enhancement sorted by
> priorities. I would like to add them as many as possible.
> == filtered vmcore utilities ==
> - in different compressed levels, verify the vmcore with the correct
> - verify it in flat file or ELF formats from a network host.
> == analyse vmcore utilities ==
> - GDB
> - crash with better error detecting.
> - crash to analyse Hypervisor and Dom0 Kernel.
> == test scripts ==
> - timestamp information for crash was triggered, vmcore was generated,
> and vmcore was verified.
> - aim to 100% automation, and reduce manual setup.
> - tidy up scripts.
> == crash scenarios ==
> - SDINT switch for ia64 if possible.
> - Hypervisor crash for Virtualization.
> - crashes on full- and para-virt guests.
> == fix bugs in existing tests ==
> - printk LKDTM module can hang the second Kernel.
> == kdump configurations and init script ==
> - capture vmcore after init runs.
> - rpm pre- and post-scripts
> - kdump_pre and kdump_post directives
Can we boost the priority of this item. Making sure all the
kdump config options are working as stated. This is the interface
a kdump user first sees and if it does not work, then it leaves a very
> == increase coverages for new kexec/kdump development efforts ==
> - new reserved region syntax in Kernel.
Another important thing we need to focus on is driver testing. Drivers
can fail to initialize in second kernel and kdump will fail. Can we do
something so that we can do following.
- Collect the machine statistics on which kdump was tested and send
the reports to a common place. Especially capture the storage/network
driver data which can be probably be available through LTP site.
- Also capture how much memory was reserved on what architecture and
whether it worked or not. This will help us verify for sure that how
much memory to reserve for second kernel on various architectures.
More information about the kexec