Bug 483123
| Summary: | No mention of Tech-Preview Status of 32-bit guest on 64-bit host in RHEL 5.2 and 5.3 release notes. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Zak Berrie <zbrown> |
| Component: | xen | Assignee: | Ryan Lerch <rlerch> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.3 | CC: | clalance, xen-maint |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-10-22 15:39:23 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: | |||
| Bug Blocks: | 492190 | ||
|
Description
Zak Berrie
2009-01-29 19:15:23 UTC
Assigning to release note writer. The note should be present in the RHEL 5.2 and 5.3 release notes. Ryan,
Well, we are kind of in a funny situation. RHEL-5.4 is going to make 32-bit guest on 64-bit host fully supported. So we won't need a release note in 5.4 anymore. However, should we still update the online release notes on 5.2 and 5.3 to say that it's still tech-preview on those releases? Or should we just close this and forget about it?
Chris Lalancette
5.4 now fully supports 32-on-64. I'm going to close this bug out now; if someone feels we should update the online 5.2 and 5.3 release notes, feel free to reopen this bug. Chris Lalancette In my opinion the documentation should be revised. I've encountered confusion on this question from customers in the field twice now. Users who are working with 5.3 don't think to read back to the 5.1 release notes and compare the two. Which is something you would have to do to see that this restriction still exists in 5.3. We also cannot assume that they'll read the 5.4 release notes either. I've encountered this in the field twice now. Thank you. |