-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-10.2
-
None
-
None
-
None
-
1
-
rhel-virt-tools
-
None
-
False
-
False
-
-
None
-
Virt-tools for next sprint
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
What were you trying to do that didn't work?
v2v fails to convert the guest with specical charactor like '*+_/' via vmx+ssh
Please provide the package NVR for which the bug is seen:
virt-v2v-2.9.10-2.el10.x86_64
libguestfs-1.57.6-2.el10.x86_64
guestfs-tools-1.54.0-7.el10.x86_64
libvirt-libs-11.10.0-1.el10.x86_64
nbdkit-1.45.12-2.el10.x86_64
libnbd-1.24.0-1.el10.x86_64
How reproducible is this bug?:
100%
Steps to reproduce
- Prepare a guest with specific characters like '*+_/' on VMware
cat esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-_+_%2f/esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-ch ars-_\+_\%2f.vmx |grep disk scsi0:0.fileName = "esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-_+_%2f.vmdk" displayName = "esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-*+_%2f" nvram = "esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-_+_%2f.nvram" migrate.hostLog = "esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-_+_%2f-78de53eb.hlog"
- Convert the guest from VMware via vmx+ssh by virt-v2v
# virt-v2v -i vmx -it ssh ssh://root@10.73.212.36/vmfs/volumes/esx8.0-function-2/esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-_+_%2f/esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-_+_%2f.vmx -ip /home/esxpwd [ 0.0] Setting up the source: -i vmx ssh://root@10.73.212.36/vmfs/volumes/esx8.0-function-2/esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-_+_%2f/esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-_+_%2f.vmx nbdkit: ssh[1]: error: /vmfs/volumes/esx8.0-function-2/esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-_+_//esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-_+_/.vmx: cannot open file for reading: SFTP server: No such file nbdcopy: nbd+unix://?socket=/tmp/v2vssh.KOZzIE/nbdkit1.sock: nbd_connect_uri: the server has no export named '': /vmfs/volumes/esx8.0-function-2/esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-_+_//esx8.0-rhel9.6-x86_64-efi-disk-name-contains-specical-chars-_+_/.vmx: cannot open file for reading: SFTP server: No such file: No such file or directory virt-v2v: error: could not copy the VMX file from the remote server, see earlier error messages If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...]
Expected results
As above description
Actual results
Fix the bug
