Description of problem: Import VM - Remap vNIC's type driver as well. Currently we are no mapping the vNICs type driver on the DR import VM flow. - If on source network 'green' is a virtIo type and we choosing to remap it to network 'blue' on destination which is 'passthrough' type, network 'blue' will be imported as virtIo type. - If on source network 'yellow' is a 'passthorugh' type and we choosing to remap it to network 'red' on destination which is virtIo type, network 'red' will be imported as 'passthroug' type. Such miss match will cause to some VMs on destination to not start. I understand that this is a big change, which requires a change of driver in the guest and can change the in-guest name of the nic. (eth0<>ens3) Version-Release number of selected component (if applicable): oVirt Engine Version: 4.2.0-0.0.master.20161225113738.git548589f.el7.centos How reproducible: 100%
We didn't get to this bug for more than 2 years, and it's not being considered for the upcoming 4.4. It's unlikely that it will ever be addressed so I'm suggesting to close it. If you feel this needs to be addressed and want to work on it please remove cond nack and target accordingly.
Closing for capacity reasons.