virtio win iso rpm consumers

This page tracks some details on how different tools are consuming the virtio-win RPM or ISO content.

virt-v2v installs viostor offline, puts the rest of the drivers (NetKVM etc) into a windows driver search path so that next VM boot will auto install the drivers.
- Rich gives a bit more detail here: https://bugzilla.redhat.com/show_bug.cgi?id=1438794#c1
- And RHEL virt-v2v documentation gives even more detail
Man page, check for virtio-win references: http://libguestfs.org/virt-v2v.1.html
Most of the code dealing with it: https://github.com/libguestfs/libguestfs/blob/master/v2v/windows_virtio.ml
prefers accessing the iso because it has more drivers than the RPM install: https://github.com/libguestfs/libguestfs/commit/543b7433e29e18fd5b272d6ba927ff3ec27cbecb

NSIS code, indicates what drivers it actually handles: https://gitlab.freedesktop.org/spice/win32/spice-nsis/blob/master/win-guest-tools.nsis
Uses extracted virtio-win.iso content as input
Generates public spice-guest-tools.exe and ovirt specific ovirt-guest-tools.iso
- ovirt infact uses a forked copy of this called ovirt-wgt (windows guest tools)
- ovirt-wgt code: https://gerrit.ovirt.org/#/admin/projects/ovirt-wgt

Uses drivers for windows unattended installs
Uses .vfd with viostor generated on demand, with txtsetup to autoinstall it
Rest of the drivers are installed on firstboot with spice-guest-tools.exe
Drivers are copied from virtio-win and hosted elsewhere, so it doesn't directly consume virtio-win on host
https://zeenix.fedorapeople.org/drivers/

Provide feedback