Bug 1217658

Summary:	Distribute a README with the RPM that explains the layout
Product:	[Community] Virtualization Tools	Reporter:	Cole Robinson <crobinso>
Component:	virtio-win	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	ailan, crobinso, ghammer, jen, lijin, michen, rjones, virt-maint, virt-maint, vrozenfe, yvugenfi
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-08 23:17:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Cole Robinson 2015-05-01 00:03:53 UTC

The virtio-win RPM contents are a bit strange, given that it's an RPM that installs and .iso, .vfd, .msi, and a bunch of binary drivers on the host machine. If you don't understand how to use the drivers already then it's certainly confusing.

We should ship a brief README at least pointing to a canonical source explaining the contents how to use them. So maybe official RHEL docs if those exist, or the fedora wiki page: https://fedoraproject.org/wiki/Windows_Virtio_Drivers

Comment 2 Cole Robinson 2015-08-10 23:48:51 UTC

Not done, and I won't get to this in the short term, so moving to 7.3

Comment 5 Cole Robinson 2017-06-06 18:10:51 UTC

Still not done and not urgent so pushing to 7.5

Comment 8 Cole Robinson 2018-05-16 23:36:40 UTC

This isn't really anything that needs to tracked as part of RHEL, so I'm just moving this to the upstream tracker. The README should really only be added once the file layout is extended to support things like bug 1223668, so it's kinda blocked on that

Comment 9 Amnon Ilan 2018-05-17 06:40:08 UTC

(In reply to Cole Robinson from comment #8)
> This isn't really anything that needs to tracked as part of RHEL, so I'm
> just moving this to the upstream tracker. 

Where is this upstream tracker? 
Should we just make bug 1223668 block the upstream tracker and close this bz?

> The README should really only be
> added once the file layout is extended to support things like bug 1223668,
> so it's kinda blocked on that

Comment 10 Cole Robinson 2018-08-08 23:17:03 UTC

(In reply to Amnon Ilan from comment #9)
> (In reply to Cole Robinson from comment #8)
> > This isn't really anything that needs to tracked as part of RHEL, so I'm
> > just moving this to the upstream tracker. 
> 
> Where is this upstream tracker? 
> Should we just make bug 1223668 block the upstream tracker and close this bz?
> 

I meant the upstream bug tracker, product=Virtualization Tools. But yeah this can just be folded into 1223668 since it's not worth adding a README until that's done IMO

*** This bug has been marked as a duplicate of bug 1223668 ***