Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 969788

Summary: [Doc] Doc-Req-650-[RFE] Add ability to pull system entropy from host
Product: Red Hat Enterprise Linux 6 Reporter: Laura Novich <lnovich>
Component: doc-Virtualization_Administration_GuideAssignee: Laura Novich <lnovich>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: high    
Version: 6.2CC: akong, amit.shah, areis, bcao, bsarathy, jhradile, juzhang, kseifried, laine, lnovich, mhomolov, michen, mkenneth, pkrempa, qzhang, rbalakri, sgrubb, shu, sradvan, tburke, virt-maint
Target Milestone: rcKeywords: Documentation, FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 786407 Environment:
Last Closed: 2014-10-16 01:03:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 786407, 973003, 973416, 973871, 989641, 1001770, 1001773    
Bug Blocks: 786408, 883503, 896690    

Comment 7 Amit Shah 2014-09-24 06:57:38 UTC
In the first paragraph, we need to mention coupling of /dev/hwrng and rngd is a manual step -- ie customers need to do it themselves, via (e.g. "rngd -b -r /dev/hwrng -o /dev/random").

This manual step is NOT needed RHEL 7.1 onwards, but needed in RHEL6 and RHEL7.0.

There is a mention of "Figure 10.15. Random number generator device", should that be removed?

Last para has "Examples of such devices are /dev/random".  Just make it singular instead of plural?

Thanks,

Comment 9 Amos Kong 2014-09-26 04:54:26 UTC
'virtio-rng' and 'virtio-RNG' are all used in this chapter, I prefer the 1st one.


"The virtio-RNG device is available for both Windows and KVM guest virtual machines"

%s/KVM guest/Linux/
The virtio-rng device is available for both Windows and Linux virtual machines.

Comment 10 Amos Kong 2014-09-26 04:56:11 UTC
<source mode='connect' host physical machine='1.2.3.4' service='1234'>

%s/host physical machine/host/

typo?

Comment 17 Amit Shah 2014-09-30 13:32:11 UTC
Just a couple of notes.  We can hot-plug the virtio-rng device as well, so a shutdown isn't the only option, as mentioned in procedure 10.11.

The libvirt backend/model description might need some editing.  I'm busy with other stuff right now so can't do a thorough review of it, asking Peter Krempa if he can do it.  Peter?

Comment 20 Amit Shah 2014-10-06 08:54:25 UTC
2nd para:
> followind
typo

2nd para:
> Refer Note for instuctions on installing the Windows requirements. Unless noted, the followind descriptions are for both Linux and Windows guests virtual and host physical machines.

"guests virtual and host physical machines" doesn't make sense.  Suppose it should be "for both Linux (rather RHEL?) and Windows guest virtual machines".

3rd para:
>  in the /dev/hwrng directory.

/dev/hwrng is a file; not a directory.  I had changed this to read "at the location /dev/hwrng" in the etherpad at http://etherpad.corp.redhat.com/g5KZlqQqGv  why wasn't that incorporated?

Section Note:
> viorng ("VirtIO RNG Device")to be installed.

Missing whitespace after closing parenthesis

The libvirt section still has redundant info.

Comment 22 Amit Shah 2014-10-07 17:07:39 UTC
Not yet to my taste.

(In reply to Amit Shah from comment #20)
> 2nd para:
> > Refer Note for instuctions on installing the Windows requirements. Unless noted, the followind descriptions are for both Linux and Windows guests virtual and host physical machines.
> 
> "guests virtual and host physical machines" doesn't make sense.  Suppose it
> should be "for both Linux (rather RHEL?) and Windows guest virtual machines".

This is still the same.

> The libvirt section still has redundant info.

And the libvirt section still looks the same.

Particularly, there are three bullets in the last para, and they all overlap.  There also is this line:
> "The EGD protocol is a simple protocol that was introduced by the entropy gathering daemon. It is a substitute for machines that don't support /dev/random. "

This is of no concern to us why the EGD was introduced -- because RHEL always has /dev/random.

We really should scratch the entire "virtio-rng elements" section and re-write it.  Please; I think this is the 5th time I'm mentioning this.

Comment 25 Dayle Parker 2014-10-16 01:03:51 UTC
This change is now available in the Red Hat Enterprise Linux 6.6 documentation at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/.