If conversion succeeds, you can create a custom SELinux policy or run the converter in permissive mode.
| Cause | Explanation | |-------|-------------| | | Converter expects bash and standard Linux commands ( lsblk , df , lvm , cat ) in a specific path. | | Missing required packages | perl , sudo , lvm2 , sg3_utils , or parted are missing. | | SSH configuration restrictions | PermitRootLogin no , AllowUsers whitelist, or MaxSessions too low. | | File system type unsupported | Btrfs, ZFS, or XFS with advanced features may not be fully discovered. | | SELinux or AppArmor blocking | Security modules block the helper script from executing or accessing /proc , /sys , or device maps. | | Converter version mismatch | Converter 6.x cannot properly query newer Linux kernels (5.10+). | If conversion succeeds, you can create a custom
fix_vmware_converter.sh
During discovery, the Converter uploads and runs a script called vmware-sysinfo.sh to the source’s /tmp directory. If /tmp is mounted with the noexec flag (a common security hardening practice), the script will fail with a "Permission Denied" error. | | SSH configuration restrictions | PermitRootLogin no