Description of problem:
Prompt confused warnings and can't find OS when v2v convert guest which has empty SATA cdrom via vmx

Version-Release number of selected component (if applicable):
virt-v2v-2.3.7-1.el9.x86_64
guestfs-tools-1.51.6-1.el9.x86_64
libguestfs-1.50.1-6.el9.x86_64
nbdkit-server-1.36.1-1.el9.x86_64
libnbd-1.18.1-3.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Prepare a guest which has empty cdrom and cdrom device type is SATA
#cat Auto-esx8.0-rhell9.3-efi-with-empty-cdrom/Aut
o-esx8.0-rhell9.3-efi-with-empty-cdrom.vmx |grep 'sata0:0'
sata0:0.startConnected = "FALSE"
sata0:0.deviceType = "cdrom-image"
sata0:0.fileName = ""
sata0:0.present = "TRUE"

2.Convert the guest from VMware via vmx by v2v

1.  virt-v2v -i vmx -it ssh ssh://root@10.73.212.36/vmfs/volumes/esx8.0-function/Auto-esx8.0-rhell9.3-efi-with-empty-cdrom/Auto-esx8.0-rhell9.3-efi-with-empty-cdrom.vmdk -ip /home/esxpwd 
   [   0.1] Setting up the source: -i vmx ssh://root@10.73.212.36/vmfs/volumes/esx8.0-function/Auto-esx8.0-rhell9.3-efi-with-empty-cdrom/Auto-esx8.0-rhell9.3-efi-with-empty-cdrom.vmdk
   (root@10.73.212.36) Password: 
   virt-v2v: warning: vmx parser: cannot parse this line, ignoring: version=1
   virt-v2v: warning: vmx parser: cannot parse this line, ignoring: 
   CID=c2e07f83
   virt-v2v: warning: vmx parser: cannot parse this line, ignoring: 
   parentCID=ffffffff
   virt-v2v: warning: vmx parser: cannot parse this line, ignoring: RW 
   25165824 VMFS "Auto-esx8.0-rhell9.3-efi-with-empty-cdrom-flat.vmdk"
   virt-v2v: warning: no displayName key found in VMX file
   [   3.2] Opening the source
   [   8.1] Inspecting the source
   virt-v2v: error: inspection could not detect the source guest (or physical 
   machine).

Assuming that you are running virt-v2v/virt-p2v on a source which is 
supported (and not, for example, a blank disk), then this should not 
happen.

No root device found in this operating system image.

If reporting bugs, run virt-v2v with debugging enabled and include the 
complete output:

  virt-v2v -v -x [...]

Actual results:
As above description

Expected result:
virt-v2v can  convert guest which has empty SATA cdrom via vmx

Additional info:
virt-v2v can  convert guest which has empty IDE cdrom via vmx

#cat Auto-esx6.7-rhel7.7-host_cd-without-filename/Auto-esx6.7-rhel7.7-host_cd-
without-filename.vmx x |grep 'ide0:0'
ide0:0.deviceType = "atapi-cdrom"
ide0:0.present = "TRUE"
ide0:0.autodetect = "TRUE"
ide0:0.fileName = ""
ide0:0.startConnected = "FALSE"

1. virt-v2v -i vmx -it ssh ssh://root@10.73.212.38/vmfs/volumes/esx6.7-6.5-function/esx6.7/Auto-esx6.7-rhel7.7-host_cd-without-filename/Auto-esx6.7-rhel7.7-host_cd-without-filename.vmx  -ip /home/esxpwd
   [   0.1] Setting up the source: -i vmx ssh://root@10.73.212.38/vmfs/volumes/esx6.7-6.5-function/esx6.7/Auto-esx6.7-rhel7.7-host_cd-without-filename/Auto-esx6.7-rhel7.7-host_cd-without-filename.vmx
   (root@10.73.212.38) Password: 
   (root@10.73.212.38) Password: 
   [   7.8] Opening the source
   [  13.4] Inspecting the source
   [  25.2] Checking for sufficient free disk space in the guest
   [  25.2] Converting Red Hat Enterprise Linux Server 7.7 Beta (Maipo) to run on KVM
   virt-v2v: This guest has virtio drivers installed.
   [ 146.3] Mapping filesystem data to avoid copying unused and blank areas
   [ 148.4] Closing the overlay
   [ 148.7] Assigning disks to buses
   [ 148.7] Checking if the guest needs BIOS or UEFI to boot
   [ 148.7] Setting up the destination: -o libvirt
   [ 152.3] Copying disk 1/1
   █ 100% [****************************************]
   [ 236.3] Creating output metadata
   [ 236.4] Finishing off