RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When using virt-p2v from the kernel command line, if the final
p2v.* parameter appears at the end of the command line, then
a \n character is appended to it.

For example, the following configuration won't work:

  APPEND [....] p2v.o=disk p2v.os=/var/tmp

because virt-p2v will try to use directory "/var/tmp\n" on
the conversion server.

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

virt-p2v upstream in <= 1.29.46, and also in RHEL 7.1

How reproducible:

100%

Steps to Reproduce:

See my steps in https://bugzilla.redhat.com/show_bug.cgi?id=1229262#c2

Actual results:

In 'systemctl status p2v -l output' you will see:

virt-v2v: error: -os /var/tmp
: output directory does not exist or is not a directory

Notice that the error message is split across two lines, indicating
an invisible \n character appearing after /var/tmp

Upstream fix:
https://github.com/libguestfs/libguestfs/commit/6114c10df05cdb1662ac22930010fd45714f9c40

The fix in comment 1 wasn't quite correct.  The following commits
are needed:

https://github.com/libguestfs/libguestfs/commit/6114c10df05cdb1662ac22930010fd45714f9c40
https://github.com/libguestfs/libguestfs/commit/fc554d422a95f0cef21073a3a8ba0b2d8ddbab45
https://github.com/libguestfs/libguestfs/commit/cca4343203f18367033a56139231ff2518ad6655
https://github.com/libguestfs/libguestfs/commit/154251b3f0312864c460533ae28a09483fb70051

Tested with:
livecd-p2v-201506091319.iso
virt-v2v-1.28.1-1.38.el7.x86_64
libguestfs-1.28.1-1.38.el7.x86_64

1.Add after APPEND [....] p2v.o=disk p2v.os=/var/tmp in kernel command line.

2.Launch virt-p2v client,conversion starts successfully without error info in description.

Refer to the above comments,move the bug to VERIFIED.

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/RHBA-2015-2183.html