Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Boot up from NVMe disk and hot-add NVMe disk fails on Oracle Linux 7.4 (52628)

Last Updated: 5/2/2018Categories: TroubleshootingTotal Views: 7652Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

In Oracle Linux 7.4 virtual machine, when you hot add new NVMe controllor and new hard disk, virtual machine poweroff and can't boot up after applying the configuration.

When you install Oracle Linux 7.4 on NVMe Hard disk, after installation finish and first reboot for virtual machine fails.

Oracle Linux 7.4 VM fails identifing new disk and dmesg has call trace:

[ 751.301157] ------------[ cut here ]------------
[ 751.301165] WARNING: CPU: 0 PID: 13261 at lib/list_debug.c:33 __list_add+0xb4/0xc0()
[ 751.301167] list_add corruption. prev->next should be next (ffffffff81be3ba0), but was ffff880034b6a6c0. (prev=ffff880034b6a6c0).
[ 751.301169] Modules linked in: fuse nvme xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun ip6t_rpfilter ipt_REJECT nf_reject_ipv4 ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter vmw_vsock_vmci_transport vsock crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel lrw gf128mul glue_helper ablk_helper cryptd ppdev vmw_balloon pcspkr sg parport_pc parport vmw_vmci i2c_piix4 shpchp acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables xfs
[ 751.301196] libcrc32c sr_mod sd_mod cdrom ata_generic pata_acpi crc32c_intel vmwgfx drm_kms_helper serio_raw ttm mptspi scsi_transport_spi ahci ata_piix mptscsih libahci drm vmxnet3 libata mptbase i2c_core dm_mirror dm_region_hash dm_log dm_mod
[ 751.301207] CPU: 0 PID: 13261 Comm: kworker/0:0 Tainted: G W 4.1.12-94.3.9.el7uek.x86_64 #2
[ 751.301209] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/28/2017
[ 751.301213] Workqueue: events nvme_dev_scan [nvme]
[ 751.301216] 0000000000000286 000000008a28953d ffff8800758cbb68 ffffffff81730f98
[ 751.301218] ffff8800758cbbc0 ffffffff81a3ae40 ffff8800758cbba8 ffffffff8108604a
[ 751.301221] ffff8800758cbbd8 ffff880034b6ae90 ffffffff81be3ba0 ffff880034b6a6c0
[ 751.301223] Call Trace:
[ 751.301228] [<ffffffff81730f98>] dump_stack+0x63/0x81
[ 751.301231] [<ffffffff8108604a>] warn_slowpath_common+0x8a/0xc0
[ 751.301233] [<ffffffff810860d5>] warn_slowpath_fmt+0x55/0x70
[ 751.301236] [<ffffffff813580a4>] __list_add+0xb4/0xc0
[ 751.301239] [<ffffffff81319f1f>] blk_mq_init_allocated_queue+0x38f/0x490
[ 751.301242] [<ffffffff8131a05a>] blk_mq_init_queue+0x3a/0x60
[ 751.301245] [<ffffffffa05c0cd2>] nvme_validate_ns+0xb2/0x340 [nvme]
[ 751.301248] [<ffffffffa05c234b>] nvme_scan_namespaces+0x16b/0x2e0 [nvme]
[ 751.301251] [<ffffffffa05c24e6>] nvme_dev_scan+0x26/0x90 [nvme]
[ 751.301254] [<ffffffff810a0b08>] process_one_work+0x158/0x460
[ 751.301257] [<ffffffff810a1302>] worker_thread+0x112/0x520
[ 751.301259] [<ffffffff810a11f0>] ? rescuer_thread+0x3e0/0x3e0
[ 751.301262] [<ffffffff810a70c8>] kthread+0xd8/0xf0
[ 751.301265] [<ffffffff810a6ff0>] ? kthread_create_on_node+0x1b0/0x1b0
[ 751.301292] [<ffffffff81738fe2>] ret_from_fork+0x42/0x70
[ 751.301297] [<ffffffff810a6ff0>] ? kthread_create_on_node+0x1b0/0x1b0
[ 751.301299] ---[ end trace ddebbde57eb9b101 ]---
[ 751.303880] nvme 0000:0b:00.0: nvme_revalidate_disk: Identify failure
[ 770.486941] nr_pdflush_threads exported in /proc is scheduled for removal

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment

Resolution

This issue is resolved in ESXi 6.5 U2,available at VMware Downloads.

To work around this issue, upgrade to UEK R4U5 or later which backport the new NVMe driver. Hot-adding NVMe disk works well on new kernel.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant