Bug 730036

Summary: CPUScaling test aborted during the test in RH5.7 x86 XEN kernel
Product: [Retired] Red Hat Hardware Certification Program Reporter: chau nguyen <chau.nguyen2>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED WONTFIX QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: czhang, gregg.shick, gwen.lapo, mfuruta, rlandry, ykawada
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-23 19:17:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Log
none
output.log none

Description chau nguyen 2011-08-11 15:32:53 UTC 
Description of problem: CPUScaling test aborted during the test in RH5.7 x86 XEN kernel



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install RH5.7 x86 XEN kernel build GA
2. Install RH certification test kits
3.Run CPUScaling test
  
Actual results:
Aborted

Expected results:
Pass

Additional info:
CPUScaling test aborted during the test in RH5.7 x86 in XEN kernel because of no physical_package_id directory.  However, there is physical_package_id directory in baremetal kernel, and the test passed without any problem.
Comment 1 chau nguyen 2011-08-12 21:16:58 UTC 
Created attachment 518109 [details]
Log
Comment 2 chau nguyen 2011-08-12 21:22:36 UTC 
Created attachment 518111 [details]
output.log
Comment 3 Rob Landry 2011-08-17 19:43:43 UTC 
Cpuscaling testing with the -xen kernel is not required.  Also as noted -xen does not currently provide physical_package_id even in dom0 which is requierd for the cpuscaling test so I'm going to go ahead and close this as not a bug given expected behavior and not a certification blocker.

A RHEL bug could be opened to request the physical package id be provided, however (and this is just a guess I do not speak for the RHEL team) but I would suspect that would be denied without some other use case.