Bug 589929

Summary: "No mapping found in config file" warning although the network mapping has already specified in virt-v2v.conf
Product: Red Hat Enterprise Linux 5 Reporter: Rita Wu <rwu>
Component: virt-v2vAssignee: Matthew Booth <mbooth>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 5.5CC: cwei, llim, mbooth, rjones
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-11 14:12:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
virt-v2v.conf
none
log from virt-inspect before conversion
none
log from LIBGUESTFS_TRACE=1 during conversion none

Description Rita Wu 2010-05-07 10:24:42 UTC
Created attachment 412292 [details]
virt-v2v.conf

Description of problem:
"No mapping found in config file" warning although the network mapping has already specified in virt-v2v.conf

Version-Release number of selected component (if applicable):
v2v-libvirt-0.8.1-1.el5
virt-v2v-0.5.3-1.el5


How reproducible:
100%

Steps to Reproduce:
1.#virt-v2v -f virt-v2v.conf -i libvirtxml -o rhev -osd nfs:/export xen-rhel55-32-pv-raw.xml
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: xen-rhel55-32-pv.raw configured with virtio drivers
  
Actual results:
as steps

Expected results:
the guest's network interface will be changes as virt-v2v.conf specified


Additional info:

Comment 1 Rita Wu 2010-05-07 10:26:13 UTC
Created attachment 412295 [details]
log from virt-inspect before conversion

Comment 2 Rita Wu 2010-05-07 10:30:22 UTC
Created attachment 412299 [details]
log from LIBGUESTFS_TRACE=1 during conversion

Comment 3 Matthew Booth 2010-05-11 14:12:37 UTC

*** This bug has been marked as a duplicate of bug 589999 ***