Bug 601028

Summary: virt-v2v| [FEAT] should give more meaningful info other than just the final result during the convert process,
Product: Red Hat Enterprise Linux 5 Reporter: Mohua Li <moli>
Component: virt-v2vAssignee: Matthew Booth <mbooth>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 5.7CC: leiwang, llim, mbooth, mkenneth, moli, mshao, rjones, rwu, ycui
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-07 10:15:27 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:

Description Mohua Li 2010-06-07 03:04:17 UTC
Description of problem:

for some guest, like ESX guest, the average convert time for a 10G disk about 1 hour, user won't get any information output until  1 hour later to have the finally information like below,

"unknown filesystem /dev/hdc
 unknown filesystem /dev/fd0
 virt-v2v: ESX4.0-RHEL4.8-x86_64 configured with virtio drivers
"

That's not good enough, we could give user different information in different phase during the process, like below, it will be helpful

"Transferring image,
 Transfer finished,

 Starting getting information of the **** guest
 Starting to modifying  the system
.........................................
"




Version-Release number of selected component (if applicable):
virt-v2v-0.6.0.3

How reproducible:
always

Steps to Reproduce:
1,convert any image with the virt-v2v command line, especially for ESX guest which need to take a long time,

  
Actual results:
see above

Expected results:
see above

Additional info:

Comment 1 RHEL Program Management 2010-09-05 07:57:23 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 6 RHEL Program Management 2011-09-07 10:15:27 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.