Description of problem: On v2v for a Windows VM, the destination VM created on the RHV side, has OS other. It should have OS type, same as the source VM, and this information is known both on CFME side, and of course on virt-v2v side. Version-Release number of selected component (if applicable): CFME-5.8.1 + v2v bug fixes/RHV-4.0.7
there is a non-trivial mapping to be done, we do not do that in RHV either
closing, since it's part of the old v2v solution.