Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 654912

Summary: On AMD host, running an F14 guest with 2 cores assigned hangs for "a long time" (several 10's of minutes) at start of boot
Product: Red Hat Enterprise Linux 5 Reporter: Zachary Amsden <zamsden>
Component: kernelAssignee: Zachary Amsden <zamsden>
Status: CLOSED NOTABUG QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: high    
Version: 5.7CC: amit.shah, berrange, bsarathy, clalance, dwmw2, ehabkost, gcosta, itamar, jaswinder, jforbes, knoel, laine, markmc, mtosatti, notting, ondrejj, qcai, quintela, scottt.tw, tburke, zamsden
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 651639 Environment:
Last Closed: 2011-02-15 11:32:42 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: 644973, 651639, 654914    
Bug Blocks: 580949    

Comment 1 Zachary Amsden 2011-01-13 23:27:00 UTC 
This is fixed upstream, should be backported into RHEL 5
Comment 2 RHEL Program Management 2011-02-01 17:03:05 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 3 Zachary Amsden 2011-02-03 13:31:28 UTC 
After careful review (I looked at the 400+ changes between RHEL6 and upstream, then the 450+ changes between RHEL5 and RHEL6 kvm), I don't think this bug is even present on RHEL5.  The AMD initial TSC fixes, which are the most important and clear bugfixes, have been backported into RHEL5 already, and the upstream changes which caused this bug to present have not been incorporated into the RHEL5 codebase.

I think the only thing we need to do here to close the bug is to simply test run an F14 guest with 2 VCPUs on an AMD processor to make sure it boots.
Comment 6 Zachary Amsden 2011-02-15 11:32:42 UTC 
This clone of the bug can be closed; it's in POST for 6.1, but I don't believe RHEL5 ever caught this particular bug.