diff --git a/supported-kdump-targets.txt b/supported-kdump-targets.txt
index f540f59..640fabc 100644
--- a/supported-kdump-targets.txt
+++ b/supported-kdump-targets.txt
@@ -39,7 +39,7 @@ storage:
         FC disks (qla2xxx, lpfc, bnx2fc, bfa)
         software initiator based iSCSI
         software RAID (mdraid)
-        hardware RAID (cciss, hpsa, megaraid_sas, mpt2sas, aacraid)
+        hardware RAID (smartpqi, hpsa, megaraid, mpt3sas, aacraid, mpi3mr)
         SCSI/SATA disks
         iSCSI HBA (all offload)
         hardware FCoE (qla2xxx, lpfc)
@@ -47,16 +47,15 @@ storage:
             please read "Note on FCoE" section below)
 
 network:
-        Hardware using kernel modules: (tg3, igb, ixgbe, sfc, e1000e, bna,
-              cnic, netxen_nic, qlge, bnx2x, bnx, qlcnic, be2net, enic,
-              virtio-net, ixgbevf, igbvf)
+        Hardware using kernel modules: (igb, ixgbe, ice, i40e, e1000e, igc,
+              tg3, bnx2x, bnxt_en, qede, cxgb4, be2net, enic, sfc, mlx4_en,
+              mlx5_core, r8169, atlantic, nfp, ionic; nicvf (aarch64 only))
         protocol: ipv4
         bonding
         vlan
         bridge
-        team
         vlan tagged bonding
-        bridge over bond/team/vlan
+        bridge over bond/vlan
 
 hypervisor:
         kvm
@@ -72,8 +71,10 @@ firmware:
         UEFI
 
 hypervisor:
-        VMWare ESXi 4.1 and 5.1
-        Hyper-V 2012 R2 (RHEL Gen1 UP Guest only)
+        VMWare ESXi 4.x 5.x would not be tested/supported any more.
+            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
 ------------------------
@@ -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="
 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
 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)