|
 |
893e0b |
Supported Kdump Targets
|
|
|
893e0b |
|
|
|
893e0b |
This document try to list all supported kdump targets, and those supported
|
|
|
893e0b |
or unknown/tech-preview targets, this can help users to decide whether a dump
|
|
|
893e0b |
solution is available.
|
|
|
893e0b |
|
|
|
893e0b |
Dump Target support status
|
|
|
893e0b |
==========================
|
|
|
893e0b |
This section tries to come up with some kind of guidelines in terms of
|
|
|
893e0b |
what dump targets are supported/not supported. Whatever is listed here
|
|
|
893e0b |
is not binding in any manner. It is just sharing of current understanding
|
|
|
893e0b |
and if something is not right, this section needs to be edited.
|
|
|
893e0b |
|
|
|
893e0b |
Following are 3 lists. First one contains supported targets. These are
|
|
|
893e0b |
generic configurations which should work and some configuration most
|
|
|
893e0b |
likely has worked in testing. Second list is known unsupported targets.
|
|
|
893e0b |
These targets we know either don't work or we don't support. And third
|
|
|
893e0b |
list is unknown/tech-preview. We either don't yet know the status of kdump
|
|
|
893e0b |
on these targets or these are under tech-preview.
|
|
|
893e0b |
|
|
|
893e0b |
Note, these lists are not set in stone and can be changed at any point of
|
|
|
893e0b |
time. Also these lists might not be complete. We will add/remove items to
|
|
|
893e0b |
it as we get more testing information. Also, there are many corner cases
|
|
|
893e0b |
which can't possibly be listed. For example in general we might be
|
|
|
893e0b |
supporting software iscsi but there might be some configurations of it
|
|
|
893e0b |
which don't work.
|
|
|
893e0b |
|
|
|
893e0b |
So if any target is listed in supported section, it does not mean it works
|
|
|
893e0b |
in all possible configurations. It just means that in common configurations
|
|
|
893e0b |
it should work but there can be issues with particular configurations which
|
|
|
893e0b |
are not supported. As we come to know of particular issues, we will keep on
|
|
|
893e0b |
updating lists accordingly.
|
|
|
893e0b |
|
|
|
893e0b |
|
|
|
893e0b |
Supported Dump targets
|
|
|
893e0b |
----------------------
|
|
|
893e0b |
storage:
|
|
|
893e0b |
LVM volume (no thinp)
|
|
|
893e0b |
FC disks (qla2xxx, lpfc, bnx2fc, bfa)
|
|
|
893e0b |
software initiator based iSCSI
|
|
|
893e0b |
software RAID (mdraid)
|
|
|
893e0b |
hardware RAID (cciss, hpsa, megaraid_sas, mpt2sas, aacraid)
|
|
|
893e0b |
SCSI/SATA disks
|
|
|
893e0b |
iSCSI HBA (all offload)
|
|
|
7a865b |
hardware FCoE (qla2xxx, lpfc)
|
|
|
7a865b |
software FCoE (bnx2fc) (Extra configuration required,
|
|
|
7a865b |
please read "Note on FCoE" section below)
|
|
|
893e0b |
|
|
|
893e0b |
network:
|
|
|
893e0b |
Hardware using kernel modules: (tg3, igb, ixgbe, sfc, e1000e, bna,
|
|
|
893e0b |
cnic, netxen_nic, qlge, bnx2x, bnx, qlcnic, be2net, enic,
|
|
|
893e0b |
virtio-net, ixgbevf, igbvf)
|
|
|
893e0b |
protocol: ipv4
|
|
|
893e0b |
bonding
|
|
|
893e0b |
vlan
|
|
|
893e0b |
bridge
|
|
|
893e0b |
team
|
|
|
893e0b |
vlan tagged bonding
|
|
|
893e0b |
bridge over bond/team/vlan
|
|
|
893e0b |
|
|
|
893e0b |
hypervisor:
|
|
|
893e0b |
kvm
|
|
|
893e0b |
xen (Supported in select configurations only)
|
|
|
893e0b |
|
|
|
893e0b |
filesystem:
|
|
|
893e0b |
ext[234]
|
|
|
893e0b |
xfs
|
|
|
893e0b |
nfs
|
|
|
893e0b |
|
|
|
893e0b |
firmware:
|
|
|
893e0b |
BIOS
|
|
|
893e0b |
UEFI
|
|
|
893e0b |
|
|
|
893e0b |
hypervisor:
|
|
|
893e0b |
VMWare ESXi 4.1 and 5.1
|
|
|
893e0b |
Hyper-V 2012 R2 (RHEL Gen1 UP Guest only)
|
|
|
893e0b |
|
|
|
893e0b |
Unsupported Dump targets
|
|
|
893e0b |
------------------------
|
|
|
893e0b |
storage:
|
|
|
893e0b |
BIOS RAID
|
|
|
893e0b |
Thin provisioning volume
|
|
|
893e0b |
Software iSCSI with iBFT (bnx2i, cxgb3i, cxgb4i)
|
|
|
893e0b |
Software iSCSI with hybrid (be2iscsi)
|
|
|
893e0b |
FCoE
|
|
|
893e0b |
legacy IDE
|
|
|
893e0b |
glusterfs
|
|
|
893e0b |
gfs2/clvm/halvm
|
|
|
893e0b |
|
|
|
893e0b |
network:
|
|
|
893e0b |
hardware using kernel modules: (sfc SRIOV, cxgb4vf, pch_gbe)
|
|
|
893e0b |
protocol: ipv6
|
|
|
893e0b |
wireless
|
|
|
893e0b |
Infiniband (IB)
|
|
|
893e0b |
vlan over bridge/team
|
|
|
893e0b |
|
|
|
893e0b |
filesystem:
|
|
|
893e0b |
btrfs
|
|
|
893e0b |
|
|
|
893e0b |
Unknown/tech-preview
|
|
|
893e0b |
--------------------
|
|
|
893e0b |
storage:
|
|
|
893e0b |
PCI Express based SSDs
|
|
|
893e0b |
|
|
|
893e0b |
hypervisor:
|
|
|
893e0b |
Hyper-V 2008
|
|
|
893e0b |
Hyper-V 2012
|
|
|
893e0b |
|
|
|
893e0b |
|
|
|
7a865b |
Note on FCoE
|
|
|
7a865b |
=====================
|
|
|
7a865b |
If you are trying to dump to a software FCoE target, you may encounter OOM
|
|
|
7a865b |
issue, because some software FCoE requires more memory to work. In such case,
|
|
|
7a865b |
you may need to increase the kdump reserved memory size in "crashkernel="
|
|
|
7a865b |
kernel parameter.
|
|
|
7a865b |
|
|
|
7a865b |
By default, RHEL systems have "crashkernel=auto" in kernel boot arguments.
|
|
|
7a865b |
The auto reserved memory size is designed to balance the coverage of use cases
|
|
|
7a865b |
and an acceptable memory overhead, so not every use case could fit in, software
|
|
|
7a865b |
FCoE is one of the case.
|
|
|
7a865b |
|
|
|
7a865b |
For hardware FCoE, kdump should work naturally as firmware will do the
|
|
|
7a865b |
initialization job. The capture kernel and kdump tools will run just fine.
|
|
|
7a865b |
|
|
|
893e0b |
Useful Links
|
|
|
893e0b |
============
|
|
|
893e0b |
[1] RHEL6: Enabling kdump for full-virt (HVM) Xen DomU
|
|
|
893e0b |
(https://access.redhat.com/knowledge/solutions/92943)
|