Description of problem: On CFME/v2v dialog, Install drivers field should: 1. Not appear for a RHEL source VM. 2. Appear or a Windows source VM. If there are no drivers installed, the driver install should be enforced (That is do not allow to run the v2v operation, unless drivers are chosen to be installed) Version-Release number of selected component (if applicable): CFME-5.8.1+v2v bug fixes. Actual results: The problem that we see now without having the above implemented, that a windows source VM that do not have drivers installed, will be imported, but will not be able to run windows (the disk type on destination should be VIRTIO, so even if source disk type was IDE, the virtio-win drivers are required) Expected results: There should be install drivers enforcement, for a windows VM, if drivers are not already installed in the source VM. Need to add a warning to user, when trying to submit the v2v operation, in such a case.
(In reply to Ilanit Stein from comment #0) > Description of problem: > On CFME/v2v dialog, Install drivers field should: > 1. Not appear for a RHEL source VM. The OS identification is done by virt-v2v, it's best to let it decide if it needs anything from the drivers iso or not. > 2. Appear or a Windows source VM. > If there are no drivers installed, the driver install should be enforced > (That is do not allow to run the v2v operation, unless drivers are chosen > to > be installed) that would be different from RHV - drivers are highly recommended, but not mandatory. > Version-Release number of selected component (if applicable): > CFME-5.8.1+v2v bug fixes. > > Actual results: > The problem that we see now without having the above implemented, > that a windows source VM that do not have drivers installed, will be > imported, > but will not be able to run windows (the disk type on destination should be > VIRTIO, so even if source disk type was IDE, the virtio-win drivers are > required) > > Expected results: > There should be install drivers enforcement, for a windows VM, if drivers > are not already installed in the source VM. > Need to add a warning to user, when trying to submit the v2v operation, in > such a case. Yes, warning is a good idea. That can be OS specific, since it's just a recommendation
Based on Michal's inputs from comment #2, and this input I got from Michal S./mbetak, on a separate session: On CFME side, there is no info on the drivers installed on the source VM, The following can't be implemented: 1. enforcement of install drivers, if the required drivers are missing. 2. list only the relevant drivers in the drivers list. Therefore, this bug is narrowed into: Add a warning similar to the warning we have on RHV, when running v2v without installing drivers. See attached RHV warning screenshot "import_warning_message.png"
Created attachment 1301745 [details] import_warning_message.png
It will be solved by checking the "Install Windows Drivers" checkbox by default when the source OS is windows. This way without selecting a driver you will get a validation message on dialog submit.
isn't it good enough now in 5.8.2?
yes, Id say so
https://github.com/ManageIQ/manageiq-content/pull/170 https://github.com/ManageIQ/manageiq-providers-ovirt/pull/76
Verified on CFME-5.9.0.14: Windows VM: "Install Windows Drivers" checkbox is checked by default. RHEL VM: "Install Windows Drivers" checkbox is NOT checked by default.