Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1483580

Summary: [Docs][VMM] Document that virtio drivers are not installed during KVM import
Product: Red Hat Enterprise Virtualization Manager Reporter: Tomáš Golembiovský <tgolembi>
Component: DocumentationAssignee: Avital Pinnick <apinnick>
Status: CLOSED CURRENTRELEASE QA Contact: Byron Gravenorst <bgraveno>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.1.5CC: apinnick, kuwei, lbopf, lsurette, mxie, ptoscano, rbalakri, rjones, srevivo, tgolembi, tzheng, ykaul
Target Milestone: ovirt-4.1.6   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-17 07:13:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomáš Golembiovský 2017-08-21 12:42:02 UTC 
When importing Windows machine from VMware or Xen, it is possible to install virtio drivers during the import process. This is not possible when importing from KVM source.

It needs to be documented that the windows drivers are not installed and we expect them to be already installed. Otherwise the VM may not be able to boot after the import. Alternatively, if the user does not want to use virtio drivers, he/she should review the configuration of the VM after the import and prior first boot to make sure virtio devices are not used.
Comment 8 Avital Pinnick 2017-10-17 07:13:35 UTC 
Updated document:

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/virtual_machine_management_guide/#Importing_a_Virtual_Machine_from_KVM