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