Red Hat Bugzilla – Bug 1296593
[RFE] v2v: notify in import dialog that attaching VirtIO drivers to Windows VM is essential.
Last modified: 2016-02-18 06:16:53 EST
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):
Screenshot of current dialog attached.
Created attachment 1112485 [details]
second import dialog
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.
moving back to post, it needs to be backported
moving back to post - to make it modified for 3.6.4 it has to be backported once more
Tomas - 3.6.4 is our GA build - this should either go to 3.6.3 or be deferred to z-stream.
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
Verified using build:
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."