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 2149811 - Copy newer versions of drivers for Win 11/Win 2019/Win 2022 during virt-v2v conversion
Summary: Copy newer versions of drivers for Win 11/Win 2019/Win 2022 during virt-v2v c...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virt-v2v
Version: 9.2
Hardware: x86_64
OS: Windows
medium
medium
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Vera
URL:
Whiteboard:
Depends On: 2012658
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-01 01:53 UTC by tingting zheng
Modified: 2023-05-09 09:01 UTC (History)
10 users (show)

Fixed In Version: virt-v2v-2.2.0-5.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 07:45:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-140990 0 None None None 2023-02-07 06:03:46 UTC
Red Hat Product Errata RHBA-2023:2313 0 None None None 2023-05-09 07:46:04 UTC

Description tingting zheng 2022-12-01 01:53:09 UTC 
Description of problem:
During virt-v2v conversion, old version of drivers are copied and installed for Win 2022/Win 2019/Win 11. We need to copy new versions of drivers for these windows guests as new versions of drivers exist in virtio-win.

Version-Release number of selected component (if applicable):
virt-v2v-2.0.7-6.el9.x86_64
virtio-win-1.9.30-0.el9_1.noarch
qemu-kvm-7.1.0-5.el9.x86_64
libguestfs-winsupport-9.2-1.el9.x86_64
libvirt-8.9.0-2.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Convert Win 2022/Win 2019/Win 11 using virt-v2v.
2.Check the log, there is something like copy guest tools from old versions of windows.

eg:Convert Win 2022, the log shows as below:
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k16/amd64/balloon.cat' -> '/Windows/Drivers/VirtIO/balloon.cat'


Actual results:
Old versions of drivers are copied for Win 11/Win 2019/Win 2022 during virt-v2v conversion.

Expected results:
Copy newer versions of drivers for Win 11/Win 2019/Win 2022 during virt-v2v conversion.

Additional info:
Comment 1 Richard W.M. Jones 2022-12-01 12:49:35 UTC 
Posted:
https://listman.redhat.com/archives/libguestfs/2022-December/030366.html
Comment 2 Richard W.M. Jones 2022-12-02 10:22:17 UTC 
Upstream in:
https://github.com/libguestfs/virt-v2v/commit/7866fecbe5223eb8dec7c5cc8882d0130ccfba44
https://github.com/libguestfs/virt-v2v/commit/7b49177e2b0c769b947ed19fa029c80282a2b93b
Comment 3 Xiaodai Wang 2022-12-06 08:57:25 UTC 
# rpm -q libguestfs virt-v2v
libguestfs-1.48.4-4.el9.x86_64
virt-v2v-2.0.7-7.el9.x86_64

# grep "copying guest tools" v2v.log 
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:guest-agent/qemu-ga-x86_64.msi' -> '//qemu-ga-x86_64.msi'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viogpudo.sys' -> '/Windows/Drivers/VirtIO/viogpudo.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viogpudo.inf' -> '/Windows/Drivers/VirtIO/viogpudo.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viogpudo.cat' -> '/Windows/Drivers/VirtIO/viogpudo.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viofs.sys' -> '/Windows/Drivers/VirtIO/viofs.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viofs.inf' -> '/Windows/Drivers/VirtIO/viofs.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viofs.cat' -> '/Windows/Drivers/VirtIO/viofs.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viostor.sys' -> '/Windows/Drivers/VirtIO/viostor.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viostor.inf' -> '/Windows/Drivers/VirtIO/viostor.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viostor.cat' -> '/Windows/Drivers/VirtIO/viostor.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/vioser.sys' -> '/Windows/Drivers/VirtIO/vioser.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/vioser.inf' -> '/Windows/Drivers/VirtIO/vioser.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/vioser.cat' -> '/Windows/Drivers/VirtIO/vioser.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/vioscsi.sys' -> '/Windows/Drivers/VirtIO/vioscsi.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/vioscsi.inf' -> '/Windows/Drivers/VirtIO/vioscsi.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/vioscsi.cat' -> '/Windows/Drivers/VirtIO/vioscsi.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viorngum.dll' -> '/Windows/Drivers/VirtIO/viorngum.dll'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viorngci.dll' -> '/Windows/Drivers/VirtIO/viorngci.dll'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viorng.sys' -> '/Windows/Drivers/VirtIO/viorng.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viorng.inf' -> '/Windows/Drivers/VirtIO/viorng.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viorng.cat' -> '/Windows/Drivers/VirtIO/viorng.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/vioinput.sys' -> '/Windows/Drivers/VirtIO/vioinput.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/vioinput.inf' -> '/Windows/Drivers/VirtIO/vioinput.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/vioinput.cat' -> '/Windows/Drivers/VirtIO/vioinput.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viohidkmdf.sys' -> '/Windows/Drivers/VirtIO/viohidkmdf.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/qemupciserial.inf' -> '/Windows/Drivers/VirtIO/qemupciserial.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/qemupciserial.cat' -> '/Windows/Drivers/VirtIO/qemupciserial.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/qemufwcfg.inf' -> '/Windows/Drivers/VirtIO/qemufwcfg.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/qemufwcfg.cat' -> '/Windows/Drivers/VirtIO/qemufwcfg.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/pvpanic.sys' -> '/Windows/Drivers/VirtIO/pvpanic.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/pvpanic.inf' -> '/Windows/Drivers/VirtIO/pvpanic.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/pvpanic.cat' -> '/Windows/Drivers/VirtIO/pvpanic.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/netkvmco.dll' -> '/Windows/Drivers/VirtIO/netkvmco.dll'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/netkvm.sys' -> '/Windows/Drivers/VirtIO/netkvm.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/netkvm.inf' -> '/Windows/Drivers/VirtIO/netkvm.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/netkvm.cat' -> '/Windows/Drivers/VirtIO/netkvm.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/balloon.sys' -> '/Windows/Drivers/VirtIO/balloon.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/balloon.inf' -> '/Windows/Drivers/VirtIO/balloon.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/balloon.cat' -> '/Windows/Drivers/VirtIO/balloon.cat'


I converted a win11 guest, correct drivers are copied as shown in above log.

But there is still a tiny problem which I think could also be fixed. The
inspect.product_name is still incorrect.

[  20.8] Converting Windows 10 Enterprise to run on KVM
Comment 4 Richard W.M. Jones 2022-12-06 09:02:56 UTC 
(In reply to Xiaodai Wang from comment #3)
> But there is still a tiny problem which I think could also be fixed. The
> inspect.product_name is still incorrect.
> 
> [  20.8] Converting Windows 10 Enterprise to run on KVM

This is the product name in Windows 11.  It looks strange, but
we have to assume it's what Microsoft intended.
Comment 5 Vera 2022-12-06 12:09:25 UTC 
# rpm -qa virt-v2v libguestfs osinfo-db libosinfo
libguestfs-1.48.4-4.el9.x86_64
osinfo-db-20221130-1.el9.noarch
libosinfo-1.10.0-1.el9.x86_64
virt-v2v-2.0.7-7.el9.x86_64

S1: Convert win11 guest via virt-v2v to rhv with -o rhv
1.1# virt-v2v -ic vpx://root.213.207/data/10.73.212.38/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0.3 -io vddk-thumbprint=09:9E:54:CF:C3:36:11:9D:7D:B6:45:E0:85:74:4D:DB:CE:24:7B:46 -o rhv -os 10.73.194.125:/home/nfs_export -ip /v2v-ops/esxpw  esx7.0-win11-x86_64 -on esx7.0-win11-x86_64-export -v -x |& tee > /virt-v2v-export-domain-win11.log█ 100% [****************************************]

S1.2 import the VM and check the info
Operating System: Windows 11
Chipset/Firmware Type: Q35 Chipset with BIOS

S2:  Convert windows11 guests via virt-v2v to rhv with -o rhv-upload
2.1  # virt-v2v -ic vpx://root.213.207/data/10.73.212.38/?no_verify=1 -o rhv-upload -of raw -os nfs_data -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /v2v-ops/rhvpasswd  -oo rhv-cafile=/v2v-ops/ca22.pem -oo rhv-cluster=Default esx7.0-win11-x86_64 -it vddk -io vddk-libdir=/home/vddk7.0.3 -io vddk-thumbprint=09:9E:54:CF:C3:36:11:9D:7D:B6:45:E0:85:74:4D:DB:CE:24:7B:46 -ip /v2v-ops/esxpw -on esx7.0-win11-x86_64-rhv-upload
[   0.9] Setting up the source: -i libvirt -ic vpx://root.213.207/data/10.73.212.38/?no_verify=1 -it vddk esx7.0-win11-x86_64
[   2.7] Opening the source
[   7.9] Inspecting the source
[  13.3] Checking for sufficient free disk space in the guest
[  13.3] Converting Windows 10 Enterprise to run on KVM
virt-v2v: This guest has virtio drivers installed.
[  18.2] Mapping filesystem data to avoid copying unused and blank areas
[  19.7] Closing the overlay
[  20.0] Assigning disks to buses
[  20.0] Checking if the guest needs BIOS or UEFI to boot
[  20.0] Setting up the destination: -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data
[  50.9] Copying disk 1/1
█ 100% [****************************************]
[ 662.6] Creating output metadata
[ 682.4] Finishing off

S2.2 Check the VM info
Operating System: Windows 10 x64
Chipset/Firmware Type: Q35 Chipset with BIOS
Comment 6 Richard W.M. Jones 2022-12-06 12:14:08 UTC 
> S2.2 Check the VM info
> Operating System: Windows 10 x64
> Chipset/Firmware Type: Q35 Chipset with BIOS

This is not expected.  Did you collect the -vx output from
this run?
Comment 9 Vera 2022-12-07 01:47:52 UTC 
(In reply to Richard W.M. Jones from comment #6)
> > S2.2 Check the VM info
> > Operating System: Windows 10 x64
> > Chipset/Firmware Type: Q35 Chipset with BIOS
> 
> This is not expected.  Did you collect the -vx output from
> this run?

Please check the attachments on the details.
Comment 10 Vera 2022-12-07 06:03:02 UTC 
# rpm -qa virt-v2v libguestfs osinfo-db libosinfo
libguestfs-1.48.4-4.el9.x86_64
osinfo-db-20221130-1.el9.noarch
libosinfo-1.10.0-1.el9.x86_64
virt-v2v-2.0.7-7.el9.x86_64

For Windows2019:
# grep "copying guest tools" /win2019-rhv-upload.log 
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:guest-agent/qemu-ga-x86_64.msi' -> '//qemu-ga-x86_64.msi'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k19/amd64/balloon.cat' -> '/Windows/Drivers/VirtIO/balloon.cat'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k19/amd64/balloon.inf' -> '/Windows/Drivers/VirtIO/balloon.inf'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k19/amd64/balloon.pdb' -> '/Windows/Drivers/VirtIO/balloon.pdb'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k19/amd64/balloon.sys' -> '/Windows/Drivers/VirtIO/balloon.sys'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k19/amd64/blnsvr.exe' -> '/Windows/Drivers/VirtIO/blnsvr.exe'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k19/amd64/blnsvr.pdb' -> '/Windows/Drivers/VirtIO/blnsvr.pdb'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:NetKVM/2k19/amd64/netkvm.cat' -> '/Windows/Drivers/VirtIO/netkvm.cat'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:NetKVM/2k19/amd64/netkvm.inf' -> '/Windows/Drivers/VirtIO/netkvm.inf'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:NetKVM/2k19/amd64/netkvm.pdb' -> '/Windows/Drivers/VirtIO/netkvm.pdb'
.....
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:vioserial/2k19/amd64/vioser.pdb' -> '/Windows/Drivers/VirtIO/vioser.pdb'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:vioserial/2k19/amd64/vioser.sys' -> '/Windows/Drivers/VirtIO/vioser.sys'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:viostor/2k19/amd64/viostor.cat' -> '/Windows/Drivers/VirtIO/viostor.cat'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:viostor/2k19/amd64/viostor.inf' -> '/Windows/Drivers/VirtIO/viostor.inf'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:viostor/2k19/amd64/viostor.pdb' -> '/Windows/Drivers/VirtIO/viostor.pdb'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:viostor/2k19/amd64/viostor.sys' -> '/Windows/Drivers/VirtIO/viostor.sys'

# grep "Converting Windows" /win2019-rhv-upload.log
[  17.4] Converting Windows Server 2019 Standard to run on KVM


For Windows2022:
# grep "copying guest tools" /win2022-rhv-upload.log 
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:guest-agent/qemu-ga-x86_64.msi' -> '//qemu-ga-x86_64.msi'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k22/amd64/balloon.cat' -> '/Windows/Drivers/VirtIO/balloon.cat'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k22/amd64/balloon.inf' -> '/Windows/Drivers/VirtIO/balloon.inf'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k22/amd64/balloon.pdb' -> '/Windows/Drivers/VirtIO/balloon.pdb'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k22/amd64/balloon.sys' -> '/Windows/Drivers/VirtIO/balloon.sys'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k22/amd64/blnsvr.exe' -> '/Windows/Drivers/VirtIO/blnsvr.exe'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:Balloon/2k22/amd64/blnsvr.pdb' -> '/Windows/Drivers/VirtIO/blnsvr.pdb'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:NetKVM/2k22/amd64/netkvm.cat' -> '/Windows/Drivers/VirtIO/netkvm.cat'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:NetKVM/2k22/amd64/netkvm.inf' -> '/Windows/Drivers/VirtIO/netkvm.inf'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:NetKVM/2k22/amd64/netkvm.pdb' -> '/Windows/Drivers/VirtIO/netkvm.pdb'
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:NetKVM/2k22/amd64/netkvm.sys' -> '/Windows/Drivers/VirtIO/netkvm.sys'

# grep "Converting Windows" /win2022-rhv-upload.log
[  18.1] Converting Windows Server 2022 Standard to run on KVM


For Windows11:
# grep "copying guest tools" /win11-rhv-upload.log 
windows: copying guest tools bits: '/usr/share/virtio-win/virtio-win.iso:guest-agent/qemu-ga-x86_64.msi' -> '//qemu-ga-x86_64.msi'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viogpudo.sys' -> '/Windows/Drivers/VirtIO/viogpudo.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viogpudo.inf' -> '/Windows/Drivers/VirtIO/viogpudo.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viogpudo.cat' -> '/Windows/Drivers/VirtIO/viogpudo.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viofs.sys' -> '/Windows/Drivers/VirtIO/viofs.sys'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viofs.inf' -> '/Windows/Drivers/VirtIO/viofs.inf'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viofs.cat' -> '/Windows/Drivers/VirtIO/viofs.cat'
windows: copying guest tools bits (via libosinfo): 'host:/usr/share/virtio-win/drivers/by-os/amd64/w11/viostor.sys' -> '/Windows/Drivers/VirtIO/viostor.sys'

# grep "Converting Windows" /win11-rhv-upload.log
[  14.7] Converting Windows 10 Enterprise to run on KVM
Comment 11 Richard W.M. Jones 2022-12-07 10:00:14 UTC 
> S2.2 Check the VM info
> Operating System: Windows 10 x64

Thanks for the debug log.  We are copying the correct drivers
in (Windows 11) and we are setting the product name and
description fields correctly:

      <Info>Windows 10 Enterprise</Info>
      <Description>windows_11</Description>

(Note product name is strange, because of Microsoft, but that
should not matter.)

So it's my belief that this is actually a bug in RHV.
virt-v2v is doing the right thing.

It may be that RHV doesn't support Windows 11, since it came
out quite recently and we're not updating RHV except for
minimal maintenance.
Comment 12 Vera 2022-12-08 10:22:02 UTC 
(In reply to Richard W.M. Jones from comment #4)
> (In reply to Xiaodai Wang from comment #3)
> > But there is still a tiny problem which I think could also be fixed. The
> > inspect.product_name is still incorrect.
> > 
> > [  20.8] Converting Windows 10 Enterprise to run on KVM
> 
> This is the product name in Windows 11.  It looks strange, but
> we have to assume it's what Microsoft intended.

Hi rjones, will you fix this issue in this bug?
Comment 13 Richard W.M. Jones 2022-12-08 10:34:59 UTC 
> > [  20.8] Converting Windows 10 Enterprise to run on KVM
> Hi rjones, will you fix this issue in this bug?

It's working correctly, so its not a bug!  (Unless you mean
some other issue?)
Comment 14 Vera 2022-12-08 11:29:52 UTC 
(In reply to Richard W.M. Jones from comment #13)
> > > [  20.8] Converting Windows 10 Enterprise to run on KVM
> > Hi rjones, will you fix this issue in this bug?
> 
> It's working correctly, so its not a bug!  (Unless you mean
> some other issue?)

As above, mark Verified:Tested.
Comment 17 Vera 2022-12-29 06:29:18 UTC 
As the versions, 
# rpm -qa libosinfo osinfo-db libguestfs virt-v2v
libguestfs-1.48.4-4.el9.x86_64
osinfo-db-20221130-1.el9.noarch
libosinfo-1.10.0-1.el9.x86_64
virt-v2v-2.0.7-7.el9.x86_64


Marking as Verified.
Comment 19 errata-xmlrpc 2023-05-09 07:45:47 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:2313
Note You need to log in before you can comment on or make changes to this bug.