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.
Bug 2187961 - [RHEL 9.3] Rebase virt-v2v to version 2.3.x
Summary: [RHEL 9.3] Rebase virt-v2v to version 2.3.x
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virt-v2v
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: mxie@redhat.com
URL:
Whiteboard:
Depends On: 2175703
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-19 09:05 UTC by Richard W.M. Jones
Modified: 2023-11-07 09:28 UTC (History)
9 users (show)

Fixed In Version: virt-v2v-2.3.4-2.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-07 08:28:57 UTC
Type: Component Upgrade
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-155118 0 None None None 2023-04-19 09:06:43 UTC
Red Hat Product Errata RHBA-2023:6376 0 None None None 2023-11-07 08:29:15 UTC

Description Richard W.M. Jones 2023-04-19 09:05:40 UTC 
Description of problem:

We currently carry 31 downstream patches in RHEL 9.2.  Trying
to backport even a simple fix for bug 2168082 was difficult as the
code has been changed and reformatted a lot upstream.

Since virt-v2v releases are backwards compatible, lets rebase
to the latest version (eg. 2.3.4) instead of backporting.

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

virt-v2v 2.3.4
Comment 2 mxie@redhat.com 2023-04-28 11:27:54 UTC 
Random testing for the bug with below builds, the problem found already has been tracked by bug
virt-v2v-2.3.4-1.el9.x86_64
libguestfs-1.50.1-3.el9.x86_64
guestfs-tools-1.50.1-2.el9.x86_64
nbdkit-server-1.34.1-1.el9.x86_64
libvirt-libs-9.2.0-1.el9.x86_64
qemu-img-8.0.0-1.el9.x86_64
virtio-win-1.9.33-0.el9_2.noarch
Comment 6 mxie@redhat.com 2023-07-13 05:48:46 UTC 
Verify the bug with below builds:
virt-v2v-2.3.4-5.el9.x86_64
virtio-win-1.9.34-0.el9_2.noarch
libguestfs-1.50.1-6.el9.x86_64
guestfs-tools-1.50.1-3.el9.x86_64
nbdkit-server-1.34.1-1.el9.x86_64
libnbd-1.16.0-1.el9.x86_64
libvirt-libs-9.5.0-0rc1.1.el9.x86_64
qemu-img-8.0.0-7.el9.x86_64

Steps:
1.Build nbdkit packages from src rpm package with regular user
$ rpmbuild --rebuild virt-v2v-2.3.4-5.el9.src.rpm 
...
+ exit 0

2.Convert a windows guest with NTFS from VMware by virt-v2v.Checkpoints of guest are passed after v2v conversion
#  virt-v2v -ic vpx://administrator%40vsphere.local.213.93/data/10.73.212.38/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.1 -io  vddk-thumbprint=1B:83:D8:5A:33:31:62:DB:BA:9E:73:6D:A8:29:14:48:3F:82:F6:FD  -ip /home/passwd  Auto-esx7.0-win2019-ntfs-3g-bitblocker --key "/dev/sda2":key:VCENTER@redhat2016 --echo-keys 
[   0.0] Setting up the source: -i libvirt -ic vpx://administrator%40vsphere.local.213.93/data/10.73.212.38/?no_verify=1 -it vddk Auto-esx7.0-win2019-ntfs-3g-bitblocker
[   1.8] Opening the source
[  50.2] Inspecting the source
[  58.5] Checking for sufficient free disk space in the guest
[  58.5] Converting Windows Server 2019 Standard to run on KVM
virt-v2v: warning: this guest has Windows Group Policy Objects (GPO) and a 
new virtio block device driver was installed.  In some circumstances, Group 
Policy may prevent new drivers from working (resulting in a 7B boot error). 
 If this happens, try disabling Group Policy before doing the conversion.
virt-v2v: This guest has virtio drivers installed.
[  75.4] Mapping filesystem data to avoid copying unused and blank areas
virt-v2v: warning: fstrim on guest filesystem /dev/mapper/cryptsda2 failed. 
 Usually you can ignore this message.  To find out more read "Trimming" in 
virt-v2v(1).

Original message: fstrim: fstrim: /sysroot/: the discard operation is not 
supported
[  76.2] Closing the overlay
[  76.5] Assigning disks to buses
[  76.5] Checking if the guest needs BIOS or UEFI to boot
[  76.5] Setting up the destination: -o libvirt
[  78.7] Copying disk 1/1
█ 100% [****************************************]
[ 512.2] Creating output metadata
[ 512.3] Finishing off

3. Set cusomter path for virtio-win, then convert a windows guest from VMware by v2v. Checkpoints of guest are passed after v2v conversion

#export VIRTIO_WIN=./virtio-win-1.9.34.iso 
  
#virt-v2v -ic vpx://administrator%40vsphere.local.213.93/data/10.73.212.38/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.1 -io  vddk-thumbprint=1B:83:D8:5A:33:31:62:DB:BA:9E:73:6D:A8:29:14:48:3F:82:F6:FD  -ip /home/passwd Auto-esx7.0-win2019-x86_64-schtasks-error
[   0.0] Setting up the source: -i libvirt -ic vpx://administrator%40vsphere.local.213.93/data/10.73.212.38/?no_verify=1 -it vddk Auto-esx7.0-win2019-x86_64-schtasks-error
[   1.8] Opening the source
[   7.3] Inspecting the source
[  12.8] Checking for sufficient free disk space in the guest
[  12.8] Converting Windows Server 2019 Standard to run on KVM
virt-v2v: This guest has virtio drivers installed.
[  28.3] Mapping filesystem data to avoid copying unused and blank areas
[  29.5] Closing the overlay
[  29.8] Assigning disks to buses
[  29.8] Checking if the guest needs BIOS or UEFI to boot
[  29.8] Setting up the destination: -o libvirt
[  31.3] Copying disk 1/1
█ 100% [****************************************]
[ 295.3] Creating output metadata
[ 295.4] Finishing off

Result:
   Also do random testing for the bug, no new problem were found, move the bug from ON_QA to VERIFIED
Comment 8 errata-xmlrpc 2023-11-07 08:28:57 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 (virt-v2v bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2023:6376
Note You need to log in before you can comment on or make changes to this bug.