Bug 665883

Summary: virt-v2v: Special character in vm name from vmware ESX not showing correct
Product: Red Hat Enterprise Linux 6 Reporter: Douglas Schilling Landgraf <dougsland>
Component: virt-v2vAssignee: Matthew Booth <mbooth>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: rjones, rwu, tzheng, whuang, yupzhang
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-v2v-0.8.2-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 665960 (view as bug list) Environment:
Last Closed: 2011-12-06 15:07:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 665960    

Description Douglas Schilling Landgraf 2010-12-27 17:11:27 UTC 
Description of problem:

If customer uses name like redhat#1 in vm names on Vmware ESX during the conversion to KVM the name will change to redhat|231

Example:

# virt-v2v -ic esx://192.168.1.13/?no_verify=1 -op default --bridge virbr0 rhel5.5#1

** HEAD https://192.168.1.13/folder/New%20Virtual%20Machine/New%20Virtual%20Machine-flat.vmdk?dcPath=ha-datacenter&dsName=Storage1
==> 401 Unauthorized
** HEAD https://192.168.1.13/folder/New%20Virtual%20Machine/New%20Virtual%20Machine-flat.vmdk?dcPath=ha-datacenter&dsName=Storage1
==> 200 OK (1s)
** GET https://192.168.1.13/folder/New%20Virtual%20Machine/New%20Virtual%20Machine-flat.vmdk?dcPath=ha-datacenter&dsName=Storage1
==> 200 OK (1481s)
virt-v2v: rhel5.5|231 configured with virtio drivers
[root@localhost ~]#


<started the vm via virtual-Manager>

# virsh
Welcome to virsh, the virtualization interactive terminal.

Type:  'help' for help with commands
      'quit' to quit

virsh # list
 Id Name                 State
----------------------------------
 5 rhel5.5|231          running

virsh #

# man ascii

<snip>
Oct   Dec   Hex   Char
 043   35    23    #
<snip>

Additional info:
========================

Other tests that I made which worked just fine:

1) #virt-v2v -ic esx://192.168.1.13/?no_verify=1 -op v2v --bridge virbr0 "rhel5(x86)"

virsh # list
 Id Name                 State
----------------------------------
 3 rhel5(x86)           running


2) #virt-v2v -ic esx://192.168.1.13/?no_verify=1 -op v2v --bridge virbr0 rhel5\(x86\)

virsh # list
 Id Name                 State
----------------------------------
 3 rhel5(x86)           running


Packages:
===================
#rpm -qa | grep v2v
virt-v2v-0.6.2-4.el6.x86_64

#rpm -qa | grep libvirt
libvirt-python-0.8.1-27.el6.x86_64
libvirt-0.8.1-27.el6.x86_64
libvirt-client-0.8.1-27.el6.x86_64
libvirt-java-0.4.5-2.el6.noarch
libvirt-java-devel-0.4.5-2.el6.noarch
libvirt-devel-0.8.1-27.el6.x86_64
Comment 3 Huang Wenlong 2011-08-22 05:38:24 UTC 
Verify this bug in virt-v2v-0.8.3-1.el6


# virt-v2v -ic  esx://10.66.72.79/?no_verify=1 -b breth0 -os r6 "ESX4.1-<x86>;1#1-2"
rwu-esx3.5-rhel4.8-x86_64_ESX35-RHEL4U8-x86_64-smp: 100% [=========================================================================]D 0h12m37s
virt-v2v: ESX4.1-<x86>;1#1-2 configured with virtio drivers.



# virsh list --all
 Id Name                 State
----------------------------------
 
 49 ESX4.1-<x86>;1#1-2   running
Comment 4 errata-xmlrpc 2011-12-06 15:07:50 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2011-1615.html