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 1883802 - -i vmx: SATA disks are not parsed
Summary: -i vmx: SATA disks are not parsed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virt-v2v
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: beta
: ---
Assignee: Laszlo Ersek
QA Contact: Vera
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-30 09:36 UTC by Pino Toscano
Modified: 2022-11-15 10:23 UTC (History)
10 users (show)

Fixed In Version: virt-v2v-2.0.7-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1883588
Environment:
Last Closed: 2022-11-15 09:55:44 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
VMX file with SATA disk (3.30 KB, text/plain)
2020-09-30 09:37 UTC, Pino Toscano 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:7968 0 None None None 2022-11-15 09:56:01 UTC

Description Pino Toscano 2020-09-30 09:36:00 UTC 
+++ This bug was initially created as a clone of Bug #1883588 +++

Description of problem:

When migrating a VMware VM that uses SATA bus for disks, virt-v2v doesn't detect the disk and the migration fails. The log file says that the VM "has no non-removable disks".

------

This is to track the work to make -i vmx in virt-v2v able to parse SATA disks:

$ virt-v2v -i vmx windows2019biosvmware.vmx --print-source
[   0.0] Opening the source -i vmx windows2019biosvmware.vmx
Source guest information (--print-source option):

    source name: w2019biosvmware
hypervisor type: vmware
       VM genid: 9f47526f-7c91-13c6-f9b4-4b2edde4d6b0
         memory: 4294967296 (bytes)
       nr vCPUs: 2
     CPU vendor: 
      CPU model: 
   CPU topology: sockets: 1 cores/socket: 2 threads/core: 1
   CPU features: 
       firmware: bios
        display: 
          video: vmvga
          sound: 
disks:

removable media:

NICs:
        Network "VM Network" mac: 00:50:56:9a:9c:7a [e1000e]
Comment 1 Pino Toscano 2020-09-30 09:37:25 UTC 
Created attachment 1717798 [details]
VMX file with SATA disk

VMX file from bug 1883588.
Comment 4 Laszlo Ersek 2022-04-18 15:20:41 UTC 
I'll investigate.
Comment 5 Laszlo Ersek 2022-04-19 15:24:55 UTC 
[v2v PATCH 0/2] recognize SATA disks in VMX files
Message-Id: <20220419152415.13356-1-lersek>
https://listman.redhat.com/archives/libguestfs/2022-April/028703.html
Comment 6 Laszlo Ersek 2022-04-21 14:09:10 UTC 
(In reply to Laszlo Ersek from comment #5)
> [v2v PATCH 0/2] recognize SATA disks in VMX files
> Message-Id: <20220419152415.13356-1-lersek>
> https://listman.redhat.com/archives/libguestfs/2022-April/028703.html

Merged upstream as commit range 291edb363e84..e7539dc6f6d1.
Comment 9 Vera 2022-05-05 08:06:20 UTC 
Verified with virt-v2v-2.0.4-1.el9.x86_64

# virt-v2v -i vmx -it ssh ssh://root.196.89/vmfs/volumes/esx6.5-function/esx6.5-rhel7.6-sata/esx6.5-rhel7.6-sata.vmx -ip /v2v-ops/esx_data_pwd --print-source
[   0.0] Setting up the source: -i vmx ssh://root.196.89/vmfs/volumes/esx6.5-function/esx6.5-rhel7.6-sata/esx6.5-rhel7.6-sata.vmx
(root.196.89) Password: 
(root.196.89) Password: 
Source guest information (--print-source option):

    source name: Auto-esx6.5-rhel7.6-sata
hypervisor type: vmware
       VM genid: 
         memory: 2147483648 (bytes)
       nr vCPUs: 1
     CPU vendor: 
      CPU model: 
   CPU topology: 
   CPU features: 
       firmware: bios
        display: 
          sound: 
disks:
	0 [sata]
removable media:
	CD-ROM [ide] in slot 2
NICs:
	Network "VM Network" mac: 00:50:56:ac:94:8c [vmxnet3]


Moving to Verified.
Comment 11 errata-xmlrpc 2022-11-15 09:55:44 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 (Low: virt-v2v security, 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/RHSA-2022:7968
Note You need to log in before you can comment on or make changes to this bug.