Bug 1323973

sorry for not accurate description of actual result, correct as "virtio-win package is not installed on rhevh-20160330.0.el7ev so that windows guests will not have virtio drivers after conversion on rhevh"

If this package is required by virt-v2v - why is it not a dependency of virt-v2v?

We need to understand if virtio-win should be a dependency of another package or not.

(In reply to Fabian Deutsch from comment #2)
> If this package is required by virt-v2v - why is it not a dependency of
> virt-v2v?

virtio-win package is not a dependency of virt-v2v, but it is necessary for virt-v2v, virtio-win package provides virtio drivers for windows guests during virt-v2v conversion

The bottom line reason is because virtio-win is on the supplemental
disk, and virt-v2v is in base RHEL.  Packages in base RHEL cannot
depend on supplemental packages.

The longer reason is that virtio-win is an optional extra.  virt-v2v
can convert Windows guests without it, although they'll use emulated
devices like IDE which is slow.  That's useful in some situations:

 - places where virtio-win is too big -- it's 70MB installed

 - architectures that don't distribute virtio-win (POWER IIRC)

 - CentOS

Anyway, if you want this, make vdsm or some other package in rhevh
depend on virtio-win.

Test on rhevm without virtio-win package,windows guest will BSOD after boot on rhev-h due to no virtio drivers,so this is really a test-blocker bug for conversion of all windows guests.

Michal, wat is the expectation here? Is it expected or recommended that we do ship virtio-win in RHEV?

I'm not fast-forwading to include virtio-win because of it's size.

I should probably say that we don't test or support the non-virtio-win
path of virt-v2v, and as Tingting points out in comment 7 there is
currently a problem converting certain VMware Windows guests without
virtio-win.  Also it's not desirable to provide customers with a
slow IDE only experience.

Using webadmin import dialog, virtio-win.iso file can be attached from ISO domain to the VM manually before the import.
I verified it using RHEL hosts and it's working properly.

right, so we don't really need it deployed on every single RHEV-H.

Tingting was concerned about the user experience of having to
attach ISOs and such.  Can we improve that?

(In reply to Richard W.M. Jones from comment #12)
> Tingting was concerned about the user experience of having to
> attach ISOs and such.  Can we improve that?

this is part of the integration. You can (and it's visually encouraged) to select the virtio-win in the import dialog. And typically you do have virtio-win in the iso domain anyway, as it is needed for any "regular" RHEV Windows VMs. So normally you don't really need to do anything.

(In reply to Michal Skrivanek from comment #13)
> (In reply to Richard W.M. Jones from comment #12)
> > Tingting was concerned about the user experience of having to
> > attach ISOs and such.  Can we improve that?
> 
> this is part of the integration. You can (and it's visually encouraged) to
> select the virtio-win in the import dialog. And typically you do have
> virtio-win in the iso domain anyway, as it is needed for any "regular" RHEV
> Windows VMs. So normally you don't really need to do anything.

Is there any doc or guide to clarify these steps for importing windows guests from rhevm GUI?

If not,I think it's better to add it somewhere,as comment 7 says if no virtio-win drivers,windows guest will BSOD.

Created attachment 1144115 [details]
2nd import dialog screenshot

In the second import dialog, when selecting destination operating system (from general tab) as Windows, the next line appears in the dialog with red fonts: 
"You have selected windows OS and have not selected VirtIO drivers. This may cause the system not to boot up."
Screenshot example attached: https://bugzilla.redhat.com/attachment.cgi?id=1144115

(In reply to Nisim Simsolo from comment #16)
> In the second import dialog, when selecting destination operating system
> (from general tab) as Windows, the next line appears in the dialog with red
> fonts: 
> "You have selected windows OS and have not selected VirtIO drivers. This may
> cause the system not to boot up."
> Screenshot example attached:
> https://bugzilla.redhat.com/attachment.cgi?id=1144115

Thanks,that makes the issue clear for users.

(In reply to tingting zheng from comment #17)

also, in general there is a note about rivers for Windows OSes in Administration guide, e.g. section 10.6.2, table 10.3, Interface (as of 3.6.4.1-0.1.el6),
and the deployment is described in 16.7.5 and 16.7.6

s/rivers/drivers/ :-)

I talked to Nisim on IRC about this and he explained how this works.
When the ISO is "attached to the VM" from that dialog, what actually
is happening is the VIRTIO_WIN environment variable is set to point
to the ISO and virt-v2v runs.  virt-v2v uses the contents of the ISO
to install drivers.

*** Bug 1324723 has been marked as a duplicate of this bug. ***