Red Hat Bugzilla – Bug 1229386
virt-p2v in non-GUI mode doesn't show any conversion progress or status
Last modified: 2016-11-03 13:53:53 EDT
Description of problem: When using no GUI mode, there is no visible indication that conversion is happening (or has failed). You have to run 'systemctl status p2v -l' to see the state of conversion. Version-Release number of selected component (if applicable): virt-p2v from git, or RHEL 7.1 How reproducible: 100% Steps to Reproduce: Please see my reproducer steps here: https://bugzilla.redhat.com/show_bug.cgi?id=1229262#c2 Actual results: virt-p2v runs invisibly (or fails invisibly), unless you study the log files on the conversion server or use the systemctl command. Expected results: virt-p2v progress should be visible on screen.
I guess we're not going to be able to fix this for RHEL 7.2. However I have updated the /etc/issue documentation to show how the user can follow the progress of virt-p2v. The commit for that is: 154251b3f0312864c460533ae28a09483fb70051
Fixed in commit 762f24c1f3ffabe7412a08f4ca302c5f614aaa9c.
I can reproduce the bug on build: virt-p2v-1.28.1-1.49.1.el7 Try to verify the bug with builds virt-p2v-1.32.5-6.el7 virt-v2v-1.32.5-6.el7.x86_64 libguestfs-1.32.5-6.el7.x86_64 Steps 1.Prepare virt-p2v-1.32.5-6.el7-no-gui boot file on pxe 2.Boot the source machine to the p2v no gui file, then the conversion could be start automatically 3.Will load some conversion info at the convert interface, but the conversion showing will stop at "perf interrupt...." after waiting for a long time, pls refer to screenshot, there is no complete percentage like p2v GUI mode 4.the conversion could finished successfully Hi rjones, As step3's result, I think p2v conversion has no complete percentage at no gui mode will confuse customer whether the conversion is started or not, could you help to fix this problem
Created attachment 1173246 [details] screenshot
We're never going to have an overall percentage. However there should be a lot more output than is shown in the screenshot. On a serial console I see extra messages like: [ 44.254435] launch-virt-p2v[772]: virt-p2v: Opening data connection for sdb ... [ 44.255421] launch-virt-p2v[772]: virt-p2v: remote log directory location: /tmp/virt-p2v-20160628-8h5khs0m [ 44.257227] launch-virt-p2v[772]: virt-p2v: Setting up the control connection ... [ 44.257975] launch-virt-p2v[772]: virt-p2v: Doing conversion ... [ 44.259635] launch-virt-p2v[772]: [ 0.0] Opening the source -i libvirtxml physical.xml [ 44.262383] launch-virt-p2v[772]: virt-v2v: warning: <target dev='sr0'> was ignored because the device name [ 44.263235] launch-virt-p2v[772]: could not be recognized [ 44.263919] launch-virt-p2v[772]: [ 0.0] Creating an overlay to protect the source from being modified etc etc Does it eventually show any further messages on the console? It might just be a bit slow. Anyway I will try without a serial console later.
I see this is a bug with the messages not being flushed properly. I have pushed the following commit to fix it: https://github.com/libguestfs/libguestfs/commit/cc38d62fdfff9dd72ecb379038e99727077f639d
https://github.com/libguestfs/libguestfs/commit/d2abfc7b486039efdfb3fa9b910e14911215b85a https://github.com/libguestfs/libguestfs/commit/b15b6e69e37cb3b6520d301442a67b9971ae8d51
Verify the bug again with build: virt-p2v-1.32.5.10-el7 Steps: 1.Prepare virt-p2v-1.32.5-10.el7-no-gui boot file on pxe 2.Boot the source machine to the p2v no gui file, then the conversion could be start automatically 3.At the conversion interface,below info was added in conversion info virt-p2v:Doing conversion... 4.After conversion was finished,below info was added in end of conversion info, details pls refer to screenshot Conversion finished successfully Result now: There is clear conversion info at p2v no GUI mode now, so the bug has been fixed So move the bug from ON_QA to VERIFIED
Created attachment 1179043 [details] virt-p2v-1.32.5-10-no-gui
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. https://rhn.redhat.com/errata/RHSA-2016-2576.html