Description of problem: When trying to import a Windows 10 VM, with disk type SCSI, The disk type, of the VM created on the RHV side is IDE, though it should be VIRTIO. Version-Release number of selected component (if applicable): CFME-5.8.1 + v2v bugs fixes/RHV-4.1.3 How reproducible: Tried twice, and got the same result. Expected results: Imported Windows VM should have it's disk type VIRTIO, regardless to the source VM disk type Additional info: * When tracking the import on RHV UI, looking at the disk type, at first when the VM is created, the type displayed is VIRTIO, and at a later stage (after several minutes) it changes to IDE. * Same Windows VM was imported via RHV RESTAPI(without setting specifically disk type)/UI, and the disk of the created VM on RHV was VIRTIO, as expected.
Created attachment 1301524 [details] virt-v2v_import_log
Created attachment 1301525 [details] evm.log
Created attachment 1301526 [details] automation.log
Created attachment 1301527 [details] production.log
Please add RHV side logs and time&name of the attempted import
Created attachment 1301562 [details] engine.log Source VM name: mb-win10 Destination VM name: win10_scsi_import Time when import VM started: 3:39 PM
@Ilanit that is a very strange behavior indeed. Can you please turn of the logging of RHV API requests and provide log/rhevm.log file. There we will find the concrete xml of the request to /externalvmimports endpoint which we can use in manual reproduction. But I don't think anything on the MIQ level should be able to change the format of the disks. Was the "sparse" disk allocation (thin provisioning) enabled when submitting the operation?
The bug was reported for a RHV with nested hosts. It can't be reproduced on another RHV, with physical host. Therefore, closing the bug.