Update supported-kdump-targets.txt
Related: bz1986667 Upstream: RHEL-only Modification based on bz link: https://bugzilla.redhat.com/show_bug.cgi?id=1986667#c11 Signed-off-by: Tao Liu <ltao@redhat.com>
This commit is contained in:
parent
b468814961
commit
9e86be70ac
@ -39,7 +39,7 @@ storage:
|
|||||||
FC disks (qla2xxx, lpfc, bnx2fc, bfa)
|
FC disks (qla2xxx, lpfc, bnx2fc, bfa)
|
||||||
software initiator based iSCSI
|
software initiator based iSCSI
|
||||||
software RAID (mdraid)
|
software RAID (mdraid)
|
||||||
hardware RAID (cciss, hpsa, megaraid_sas, mpt2sas, aacraid)
|
hardware RAID (smartpqi, hpsa, megaraid, mpt3sas, aacraid, mpi3mr)
|
||||||
SCSI/SATA disks
|
SCSI/SATA disks
|
||||||
iSCSI HBA (all offload)
|
iSCSI HBA (all offload)
|
||||||
hardware FCoE (qla2xxx, lpfc)
|
hardware FCoE (qla2xxx, lpfc)
|
||||||
@ -47,16 +47,15 @@ storage:
|
|||||||
please read "Note on FCoE" section below)
|
please read "Note on FCoE" section below)
|
||||||
|
|
||||||
network:
|
network:
|
||||||
Hardware using kernel modules: (tg3, igb, ixgbe, sfc, e1000e, bna,
|
Hardware using kernel modules: (igb, ixgbe, ice, i40e, e1000e, igc,
|
||||||
cnic, netxen_nic, qlge, bnx2x, bnx, qlcnic, be2net, enic,
|
tg3, bnx2x, bnxt_en, qede, cxgb4, be2net, enic, sfc, mlx4_en,
|
||||||
virtio-net, ixgbevf, igbvf)
|
mlx5_core, r8169, atlantic, nfp, ionic; nicvf (aarch64 only))
|
||||||
protocol: ipv4
|
protocol: ipv4
|
||||||
bonding
|
bonding
|
||||||
vlan
|
vlan
|
||||||
bridge
|
bridge
|
||||||
team
|
|
||||||
vlan tagged bonding
|
vlan tagged bonding
|
||||||
bridge over bond/team/vlan
|
bridge over bond/vlan
|
||||||
|
|
||||||
hypervisor:
|
hypervisor:
|
||||||
kvm
|
kvm
|
||||||
@ -72,8 +71,10 @@ firmware:
|
|||||||
UEFI
|
UEFI
|
||||||
|
|
||||||
hypervisor:
|
hypervisor:
|
||||||
VMWare ESXi 4.1 and 5.1
|
VMWare ESXi 4.x 5.x would not be tested/supported any more.
|
||||||
Hyper-V 2012 R2 (RHEL Gen1 UP Guest only)
|
only support ESXi 6.6, 6.7, 7.0
|
||||||
|
Hyper-V 2012 R2 (RHEL Gen1 UP Guest only), later version will
|
||||||
|
also be tested/supported
|
||||||
|
|
||||||
Unsupported Dump targets
|
Unsupported Dump targets
|
||||||
------------------------
|
------------------------
|
||||||
@ -114,15 +115,5 @@ issue, because some software FCoE requires more memory to work. In such case,
|
|||||||
you may need to increase the kdump reserved memory size in "crashkernel="
|
you may need to increase the kdump reserved memory size in "crashkernel="
|
||||||
kernel parameter.
|
kernel parameter.
|
||||||
|
|
||||||
By default, RHEL systems have "crashkernel=auto" in kernel boot arguments.
|
|
||||||
The auto reserved memory size is designed to balance the coverage of use cases
|
|
||||||
and an acceptable memory overhead, so not every use case could fit in, software
|
|
||||||
FCoE is one of the case.
|
|
||||||
|
|
||||||
For hardware FCoE, kdump should work naturally as firmware will do the
|
For hardware FCoE, kdump should work naturally as firmware will do the
|
||||||
initialization job. The capture kernel and kdump tools will run just fine.
|
initialization job. The capture kernel and kdump tools will run just fine.
|
||||||
|
|
||||||
Useful Links
|
|
||||||
============
|
|
||||||
[1] RHEL6: Enabling kdump for full-virt (HVM) Xen DomU
|
|
||||||
(https://access.redhat.com/knowledge/solutions/92943)
|
|
||||||
|
Loading…
Reference in New Issue
Block a user