Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1945549

Summary: Delete or improve the warning info about rhev-apt during v2v converting windows guest on rhel9
Product: Red Hat Enterprise Linux 9 Reporter: mxie <mxie>
Component: virt-v2vAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Vera <vwu>
Severity: low Docs Contact:
Priority: low    
Version: 9.0CC: chhu, jsuchane, juzhou, mzhan, rjones, tyan, tzheng, xiaodwan
Target Milestone: betaKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-v2v-1.45.2-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-07 21:35:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description mxie@redhat.com 2021-04-01 09:26:56 UTC
Description of problem:
Delete or improve the warning info about rhev-apt during v2v converting windows guest on rhel9

Version-Release number of selected component (if applicable):
virt-v2v-1.43.3-2.el9.x86_64


How reproducible:
100%

Steps to Reproduce:
1.Convert a windows guest from VMware by v2v, there is warning info about rhev-apt during conversion

# virt-v2v -i vmx -it ssh ssh://root.199.217/vmfs/volumes/esx7.0-matrix/esx7.0-win10-x86_64/esx7.0-win10-x86_64.vmx  -o rhv-upload -of qcow2 -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -ip /home/passwd -op /home/rhvpasswd  -os nfs_data -b ovirtmgmt 
[   0.9] Opening the source -i vmx ssh://root.199.217/vmfs/volumes/esx7.0-matrix/esx7.0-win10-x86_64/esx7.0-win10-x86_64.vmx
[   2.5] Creating an overlay to protect the source from being modified
[   2.8] Opening the overlay
[   9.5] Inspecting the overlay
[  17.3] Checking for sufficient free disk space in the guest
[  17.3] Estimating space required on target for each disk
[  17.3] Converting Windows 10 Enterprise to run on KVM
virt-v2v: warning: /usr/share/virt-tools/rhev-apt.exe is missing, but the 
output hypervisor is oVirt or RHV.  Installing RHEV-APT in the guest would 
mean the guest is automatically updated with new drivers etc.  You may wish 
to install RHEV-APT manually after conversion.
virt-v2v: warning: there is no QXL driver for this version of Windows (10.0 
x86_64).  virt-v2v looks for this driver in 
/usr/share/virtio-win/virtio-win.iso

The guest will be configured to use a basic VGA display driver.
virt-v2v: This guest has virtio drivers installed.
[  26.1] Mapping filesystem data to avoid copying unused and blank areas
virt-v2v: warning: fstrim on guest filesystem /dev/sda2 failed.  Usually 
you can ignore this message.  To find out more read "Trimming" in 
virt-v2v(1).

Original message: fstrim: fstrim: /sysroot/: FITRIM ioctl failed: Device or 
resource busy
virt-v2v: warning: fstrim on guest filesystem /dev/sda1 failed.  Usually 
you can ignore this message.  To find out more read "Trimming" in 
virt-v2v(1).

Original message: fstrim: fstrim: /sysroot/: FITRIM ioctl failed: Device or 
resource busy
[  27.2] Closing the overlay
[  27.5] Assigning disks to buses
[  27.5] Checking if the guest needs BIOS or UEFI to boot
[  27.5] Initializing the target -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -os nfs_data
[  29.0] Copying disk 1/1 to qemu URI json:{ "file.driver": "nbd", "file.path": "/tmp/v2vnbdkit.TLOHWo/nbdkit4.sock", "file.export": "/" } (qcow2)
    (100.00/100%)
[1129.8] Creating output metadata
[1131.0] Finishing off

2. Found rhev-apt has been removed from virt-v2v
# ls /usr/share/virt-tools/
rhsrvany.exe


Actual results:
RHEV-apt has been removed from rhel9 virt-v2v, so the warning info about rhev-apt need to be deleted/improved

Expected results:
Should delete or improve the warning info about rhev-apt during v2v converting windows guest on rhel9, maybe below warning info about rhev-apt would be better:

virt-v2v: warning: /usr/share/virt-tools/rhev-apt.exe has been deprecated, but if the 
output hypervisor is oVirt or RHV < 4.4.  Installing RHEV-APT in the guest would 
mean the guest is automatically updated with new drivers etc.  You may wish 
to install RHEV-APT manually after conversion.



Additional info:

Comment 1 Richard W.M. Jones 2021-04-01 09:33:24 UTC
The plan here is to remove rhev-apt entirely from virt-v2v once most
customers are using RHV 4.4 (which no longer needs it).

Comment 2 Richard W.M. Jones 2021-06-22 16:15:39 UTC
Upstream I've removed RHEV-APT support after discussion with
Michal Skrivanek and Tomas Golembiovsky:

https://github.com/libguestfs/virt-v2v/commit/ef7bffe5699cd2ecd7b76d5d4dcf802861d85e55

Comment 6 Vera 2021-07-05 09:39:05 UTC
Reproduced the bug with virt-v2v-1:1.44.0-1.el9.1.x86_64.

# virt-v2v -i vmx -it ssh ssh://root.75.219/vmfs/volumes/esx6.7-matrix/esx6.7-win2016-x86_64/esx6.7-win2016-x86_64.vmx -o rhv-upload -of raw -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -ip /tmp/v2v_vpx_passwd -op /tmp/rhv_upload_passwd_file  -os nfs_data -b ovirtmgmt 
[   0.5] Opening the source -i vmx ssh://root.75.219/vmfs/volumes/esx6.7-matrix/esx6.7-win2016-x86_64/esx6.7-win2016-x86_64.vmx
[   1.8] Creating an overlay to protect the source from being modified
[   2.0] Opening the overlay
[   7.6] Inspecting the overlay
[  14.4] Checking for sufficient free disk space in the guest
[  14.4] Estimating space required on target for each disk
[  14.4] Converting Windows Server 2016 Standard to run on KVM
virt-v2v: warning: /usr/share/virt-tools/rhev-apt.exe is missing, but the 
output hypervisor is oVirt or RHV.  Installing RHEV-APT in the guest would 
mean the guest is automatically updated with new drivers etc.  You may wish 
to install RHEV-APT manually after conversion.
virt-v2v: warning: there is no QXL driver for this version of Windows (10.0 
x86_64).  virt-v2v looks for this driver in 
/usr/share/virtio-win/virtio-win.iso

The guest will be configured to use a basic VGA display driver.
virt-v2v: This guest has virtio drivers installed.
[  23.2] Mapping filesystem data to avoid copying unused and blank areas
[  23.7] Closing the overlay
[  23.9] Assigning disks to buses
[  23.9] Checking if the guest needs BIOS or UEFI to boot
[  23.9] Initializing the target -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /tmp/rhv_upload_passwd_file -os nfs_data
[  25.2] Copying disk 1/1 to qemu URI json:{ "file.driver": "nbd", "file.path": "/tmp/v2vnbdkit.Ke9Pbg/nbdkit4.sock", "file.export": "/" } (raw)
.....
#


Verify the bug with build: virt-v2v-1:1.45.2-1.el9.x86_64.

Steps:
1. check rhev-apt has been removed from virt-v2v
# ls /usr/share/virt-tools/
rhsrvany.exe


2. Convert a windows guest from VMware by v2v, there is warning info about rhev-apt during conversion
# virt-v2v -i vmx -it ssh ssh://root.75.219/vmfs/volumes/esx6.7-matrix/esx6.7-win2012-x86_64/esx6.7-win2012-x86_64.vmx -o rhv-upload -of raw -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -ip /tmp/v2v_vpx_passwd -op /tmp/rhv_upload_passwd_file  -os nfs_data -b ovirtmgmt 
[   0.8] Opening the source -i vmx ssh://root.75.219/vmfs/volumes/esx6.7-matrix/esx6.7-win2012-x86_64/esx6.7-win2012-x86_64.vmx
[   2.2] Creating an overlay to protect the source from being modified
[   2.4] Opening the overlay
[   7.2] Inspecting the overlay
[  16.1] Checking for sufficient free disk space in the guest
[  16.1] Converting Windows Server 2012 Standard to run on KVM
virt-v2v: warning: there is no QXL driver for this version of Windows (6.2 
x86_64).  virt-v2v looks for this driver in 
/usr/share/virtio-win/virtio-win.iso

The guest will be configured to use a basic VGA display driver.
virt-v2v: This guest has virtio drivers installed.
[  23.3] Mapping filesystem data to avoid copying unused and blank areas
[  23.7] Closing the overlay
[  24.0] Assigning disks to buses
[  24.0] Checking if the guest needs BIOS or UEFI to boot
[  24.0] Initializing the target -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /tmp/rhv_upload_passwd_file -os nfs_data
[  25.2] Copying disk 1/1 to qemu URI json:{ "file.driver": "nbd", "file.path": "/tmp/v2vnbdkit.RLtFHt/nbdkit4.sock", "file.export": "/" } (raw)
    (100.00/100%)
[1291.8] Creating output metadata
[1292.6] Finishing off

Result:
  The bug has been fixed, so move the bug from ON_QA to VERIFIED