Bug 1296593

Summary: [RFE] v2v: notify in import dialog that attaching VirtIO drivers to Windows VM is essential.
Product: [oVirt] ovirt-engine Reporter: Nisim Simsolo <nsimsolo>
Component: BLL.VirtAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.6.1CC: bugs, istein, nsimsolo, sbonazzo, tjelinek
Target Milestone: ovirt-3.6.3Flags: michal.skrivanek: ovirt-3.6.z?
rule-engine: planning_ack?
tjelinek: devel_ack+
rule-engine: testing_ack+
Target Release: 3.6.3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-18 11:16:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
second import dialog none

Description Nisim Simsolo 2016-01-07 15:51:27 UTC 
Description of problem:
- When importing Windows VM from VMware, the imported VM disk interface is VirtIO.
- Running imported VM without VirtIO drivers installed, leads to BSOD and it is impossible to install VirtIO drivers on this VM.
- The only way to make it run properly, is by attaching VirtIO drivers to VM during import process.
- Currently, it is unclear that VirtIO-drivers are essential for Windows based VMs. It would be nice to have a notification for it in second import dialog when selecting Windows OS in "operating system" dropbox.

Version-Release number of selected component (if applicable):
rhevm-3.6.2-0.1.el6


Additional info:
Screenshot of current dialog attached.
Comment 1 Nisim Simsolo 2016-01-07 15:54:35 UTC 
Created attachment 1112485 [details]
second import dialog
Comment 2 Shahar Havivi 2016-01-18 09:48:09 UTC 
We cannot determine that the os is Windows only virt-v2v knows when it start the process.
Its not a must to set the virtio drivers via oVirt since it can be installed by the user on the host locally.
Comment 3 Tomas Jelinek 2016-02-01 10:09:20 UTC 
moving back to post, it needs to be backported
Comment 4 Tomas Jelinek 2016-02-02 10:51:53 UTC 
moving back to post - to make it modified for 3.6.4 it has to be backported once more
Comment 5 Yaniv Kaul 2016-02-04 13:45:03 UTC 
Tomas - 3.6.4 is our GA build - this should either go to 3.6.3 or be deferred to z-stream.
Comment 6 Tomas Jelinek 2016-02-04 15:24:04 UTC 
Left the 3.6.4 there just in case it will not make it to 3.6.3... But it is merged, so changing target to 3.6.3
Comment 7 Nisim Simsolo 2016-02-11 14:56:17 UTC 
Verified using build:
rhevm-3.6.3.1-0.1.el6

Now, when selecting windows OS during import dialog, the next notification appear with red fonts:
"You have selected windows OS and have not selected VirtIO drivers. This may cause the system not to boot up."