Hello, VMWare LVM partitions are not recognized by the 5.4.126+ LT kernels; it sees the base /dev/sda disk, but thats its, stalls, fails to Boot trying to access "/dev/mapper/...." Kernels 5.4.125 and prior DO WORK, but 5.4.126+ DO NOT. I have been able to isolate the kernel failing to commit "1e209effe36cbf0a939844bcf9defd3fe1e2f593" in LT kernel 5.4.126. [And Yes the "rd.lvm.lv=" and VG/LV names match the grub line (ie. lvs -o vg_name,lv_name)] So commit "1e209effe36cbf0a939844bcf9defd3fe1e2f593" BREAKS kernel recognition of VMWare LVM partitions (but yes kernel DOES see /dev/sda but thats it). This is on ESX 6.7. Thanks
Forgot to add other specs (if it helps) ... Centos 7.9.2009 (though i dont think minor version matters) LVM 2.02.187
Update: Testing with Kernel 5.13.x (specifically 5.13.13) - Still fails to Pickup LVM partitions on /dev/sda (which is detected) in VMWare. VM Container Specs: attached in screen print Where boot stops loading: attached in screen print
Created attachment 300289 [details] vmware specs
Created attachment 300290 [details] boot failure
> Update: Testing with Kernel 5.13.x (specifically 5.13.13) - Still > fails to Pickup LVM partitions on /dev/sda (which is detected) in > VMWare. 5.13 is no longer supported. The fix was merged in 5.16: 142c779d05d1 ("scsi: vmw_pvscsi: Set residual data length conditionally") and I believe it has been backported to all the currently supported stable releases.
wow thanks - I will pull one down (after confirming the 142c779d05d1 buildin) and test!
Yah, looks like 5.15.13, 5.10.90, 5.4.170, 4.19.224, 4.14.261 and likely other current LT kernels have this fix. Now to test, prolly tomorrow; maybe tonight excited about the fix!!
@Martin -- yah!! it works!! (testing kernel 5.15.13)
This bug affects RHEL-9 (beta). A bug report submitted and being tracked: https://bugzilla.redhat.com/show_bug.cgi?id=2048178 Unfortunately it was made private, so not visible publicly.