Description of problem:
./v2v/run-v2v-locally -ic qemu+ssh://email@example.com/system -o rhev -osd blue:/export/export winxp-minimal
mount_ro: /dev/sda on /temp/transferZXQLtK: mount: you must specify the filesystem type at /home/mbooth/src/virt-v2v/blib/lib/Sys/VirtV2V/Converter/Windows.pm line 189.
virt-v2v: Failed to unmount blue:/export/export. Command exited with status 16. Output was: umount.nfs: /tmp/EfF2OGpxfX: device is busy
umount.nfs: /tmp/EfF2OGpxfX: device is busy
virt-v2v: Failed to remove mount directory /tmp/EfF2OGpxfX: Device or resource busy
The same issue was fixed for Linux guests in f4823727dd67f59e405162714210bfe9feef4970.
Version-Release number of selected component (if applicable):
Fix posted: https://www.redhat.com/archives/libguestfs/2010-May/msg00148.html
Fixed in 0.6.0-3.el5
What is the expected result? The output I got is about Parse.pm, not the transfer or Config.pm you mentioned in comment 1.
Here are my steps:
1. Uncomment Windows app in virt-v2v.conf
2. run v2v:
# virt-v2v -i libvirtxml -o rhev -osd 10.66.70.xx:/v2v/fcp_export win2k8-32.xml
virt-v2v: Unable to parse config file /etc/virt-v2v.conf:
not well-formed (invalid token) at line 161, column 6, byte 6067 at
You only hit this bug when there was no config file at all. Since 0.6.0, virt-v2v now uses /etc/virt-v2v.conf by default if no config file is specified, so to hit this bug you'd need to remove that file and not specify a replacement.
Incidentally, it sounds like you introduced a typo in your config file. That error is from the XML parser. You'd only get that if it wasn't valid XML.
Verified on virt-v2v-0.6.0-3.el5 + v2v-libvirt-0.8.1-1.el5
Now it will point "No config specified" when there is no config file.
1. Rename virt-v2v.conf
# ll /etc/virt-v2v.conf.
2. Run v2v
============For Windows guest==============
# virt-v2v -i libvirtxml -o rhev -osd 10.66.90.115:/vol/v2vwulinglu/wulingluv2v/fcp_export /tmp/win2008-32.raw.xml
virt-v2v: No config specified. No app match for os='windows' name='viostor'
major='6' minor='0' arch='i386'
virt-v2v: Failed to unmount 10.66.90.115:/vol/v2vwulinglu/wulingluv2v/fcp_export. Command exited with status 1. Output was: umount: /tmp/ZoqnQv8Gy0: device is busy
umount: /tmp/ZoqnQv8Gy0: device is busy
virt-v2v: Failed to remove mount directory /tmp/ZoqnQv8Gy0: Device or
========For Linux guest=============
# virt-v2v -i libvirtxml -o rhev -osd 10.66.90.115:/vol/v2vwulinglu/wulingluv2v/fcp_export xen-rhel55-64-pv-raw.xml
virt-v2v: No config specified. No capability match for os='linux' name='virtio' distro='rhel' major='5' minor='5'
virt-v2v: WARNING: No mapping found for bridge interface xenbr0 in config file. The converted guest may not start until its network interface is updated.
virt-v2v: rhel55-64 configured without virtio drivers
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.