Do the RHEL7 customers have access to signed drivers? If so, we could install links to those in /var/cache/gnome-boxes as part of gnome-boxes package so once the following bug is fixed, Boxes will use those drivers instead of downloading from internet:

https://bugzilla.gnome.org/show_bug.cgi?id=698144

This will also take care of bug#1032524.

(In reply to Zeeshan Ali from comment #2)
> Do the RHEL7 customers have access to signed drivers?

I don't know, I have seen contradicting answers regarding this :-/

(In reply to Christophe Fergeau from comment #3)
> (In reply to Zeeshan Ali from comment #2)
> > Do the RHEL7 customers have access to signed drivers?
> 
> I don't know, I have seen contradicting answers regarding this :-/

In that case, maybe we should postpone this to 7.1? I'll already get try to get the related upstream bug fixed in the meantime so when we get more certain info, its very easy to fix this then.

Based on comment#4.

For the other 2 steps in comment#14, I filed separate bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1054905
https://bugzilla.redhat.com/show_bug.cgi?id=1054906

I realized that step#1 I mentioned is really actually covered already as Ronan said in comment#15 and I was just looking at the wrong package (RHEL 6.5).
-----------------

There is one more thing I realized. The virtio-win package provides the driver files and if I recall correctly I failed to find a way to at least tell winxp (I think there was a way for win7) to install those drivers and that is why I used spice-guest-tools executable that I ran at the end of the installation from my installation script.

There is a way to pass preinstallation drivers to winxp but that is restricted to some particular device types. virtio-block is currently installed using that method.

Do we happen to have spice-guest-tools binary with signed drivers available?

Do we care anymore about winxp much now that MS is dropping the support?

(In reply to Zeeshan Ali from comment #19)
> For the other 2 steps in comment#14, I filed separate bugs:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1054905
> https://bugzilla.redhat.com/show_bug.cgi?id=1054906
> 
> I realized that step#1 I mentioned is really actually covered already as
> Ronan said in comment#15 and I was just looking at the wrong package (RHEL
> 6.5).
> -----------------
> 
> There is one more thing I realized. The virtio-win package provides the
> driver files and if I recall correctly I failed to find a way to at least
> tell winxp (I think there was a way for win7) to install those drivers and
> that is why I used spice-guest-tools executable that I ran at the end of the
> installation from my installation script.

Indeed, XP's end of life is in less than 3 months. We do our best to slow down our XP activity.
XP/2003 will let you use non-inbox (external), boot-time drivers, only if you take them from a Floppy disk. Than's why we provide the necessary drivers in a VFD file. This means that you can USE virtio-blk DURING the installation. You can always install drivers from the ISO, but they cannot be used already during the installation.

> 
> There is a way to pass preinstallation drivers to winxp but that is
> restricted to some particular device types. virtio-block is currently
> installed using that method.
> 
> Do we happen to have spice-guest-tools binary with signed drivers available?

Not in my domain.

And to your previous question.
RHEL customers that install boxes are entitled for the WHQLd drivers from the supplementary channel. Fedora and upstream are not.

Ronen.

> 
> Do we care anymore about winxp much now that MS is dropping the support?

(In reply to Ronen Hod from comment #20)
> (In reply to Zeeshan Ali from comment #19)
> > For the other 2 steps in comment#14, I filed separate bugs:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=1054905
> > https://bugzilla.redhat.com/show_bug.cgi?id=1054906
> > 
> > I realized that step#1 I mentioned is really actually covered already as
> > Ronan said in comment#15 and I was just looking at the wrong package (RHEL
> > 6.5).
> > -----------------
> > 
> > There is one more thing I realized. The virtio-win package provides the
> > driver files and if I recall correctly I failed to find a way to at least
> > tell winxp (I think there was a way for win7) to install those drivers and
> > that is why I used spice-guest-tools executable that I ran at the end of the
> > installation from my installation script.
> 
> Indeed, XP's end of life is in less than 3 months. We do our best to slow
> down our XP activity.
> XP/2003 will let you use non-inbox (external), boot-time drivers, only if
> you take them from a Floppy disk. Than's why we provide the necessary
> drivers in a VFD file. This means that you can USE virtio-blk DURING the
> installation. You can always install drivers from the ISO, but they cannot
> be used already during the installation.

OK, I guess there is no choice but to only install virtio-blk driver for XP then.

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

We already have all the infra on libosinfo / osinfo-db in place, we only need the data from virtio-win drivers (for "Workstation" releases of Windows, "Server" ones are not being considered now).

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (libosinfo bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4758