Previously, servers with AMD Opterom G5 processors were wrongly being recognized as AMD Operton G4 on the "View CPU Details" page in Red Hat Enterprise Virtualization Manager.
Now, the CPU flags in the Manager have been altered to detect processor model AMD Opterom G5. As a result, the Manger correctly detects when a host has and AMD Opterom G5 processor.
_G2; 4:AMD Opteron G3:svm,nx,model_Opteron_G3:Opteron_G3; 5:AMD Opteron G4:svm,nx,model_Opteron_G4:Opteron_G4; 6:AMD Opteron G5:smx,nx,model_Opteron_G5:Opteron_G5;','3.2');
_G2; 4:AMD Opteron G3:svm,nx,model_Opteron_G3:Opteron_G3; 5:AMD Opteron G4:svm,nx,model_Opteron_G4:Opteron_G4; 6:AMD Opteron G5:smx,nx,model_Opteron_G5:Opteron_G5;','3.3');
G3:Opteron_G3; 5:AMD Opteron G4:svm,nx,model_Opteron_G4:Opteron_G4;','3.1');
ron_G2; 4:AMD Opteron G3:svm,nx,model_Opteron_G3:Opteron_G3; 5:AMD Opteron G4:svm,nx,model_Opteron_G4:Opteron_G4; 6:AMD Opteron G5:smx,nx,model_Opteron_G5:Opteron_G5;','3.2');
bug is the G5 model has "smx,nx" should be "svm,nx"
you can easily fix in customer site by updating the customer db by running:
select fn_db_update_config_value('ServerCPUList',...)
where ... is the full line from packaging/dbscripts/upgrade/pre_upgrade/0000_config.sql changed from smx to svm.
for both 3.2 and 3.3 (notice in 3.3 the file only has add_config for 3.3, you need to run it as update_config of course).
UPDATE vdc_options SET option_value='3:Intel Conroe Family:vmx,nx,model_Conroe:Conroe; 4:Intel Penryn Family:vmx,nx,model_Penryn:Penryn; 5:Intel Nehalem Family:vmx,nx,model_Nehalem:Nehalem; 6:Intel Westmere Family:aes,vmx,nx,model_Westmere:West
mere; 7:Intel SandyBridge Family:vmx,nx,model_SandyBridge:SandyBridge; 8:Intel Haswell:vmx,nx,model_Haswell:Haswell; 2:AMD Opteron G1:svm,nx,model_Opteron_G1:Opteron_G1; 3:AMD Opteron G2:svm,nx,model_Opteron_
G2:Opteron_G2; 4:AMD Opteron G3:svm,nx,model_Opteron_G3:Opteron_G3; 5:AMD Opteron G4:svm,nx,model_Opteron_G4:Opteron_G4; 6:AMD Opteron G5:svm,nx,model_Opteron_G5:Opteron_G5;' WHERE option_id="258";
Is what I need to fire, correct? Please verify so that I can pass it to customer.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2014-0506.html
_G2; 4:AMD Opteron G3:svm,nx,model_Opteron_G3:Opteron_G3; 5:AMD Opteron G4:svm,nx,model_Opteron_G4:Opteron_G4; 6:AMD Opteron G5:smx,nx,model_Opteron_G5:Opteron_G5;','3.2'); _G2; 4:AMD Opteron G3:svm,nx,model_Opteron_G3:Opteron_G3; 5:AMD Opteron G4:svm,nx,model_Opteron_G4:Opteron_G4; 6:AMD Opteron G5:smx,nx,model_Opteron_G5:Opteron_G5;','3.3'); G3:Opteron_G3; 5:AMD Opteron G4:svm,nx,model_Opteron_G4:Opteron_G4;','3.1'); ron_G2; 4:AMD Opteron G3:svm,nx,model_Opteron_G3:Opteron_G3; 5:AMD Opteron G4:svm,nx,model_Opteron_G4:Opteron_G4; 6:AMD Opteron G5:smx,nx,model_Opteron_G5:Opteron_G5;','3.2'); bug is the G5 model has "smx,nx" should be "svm,nx" you can easily fix in customer site by updating the customer db by running: select fn_db_update_config_value('ServerCPUList',...) where ... is the full line from packaging/dbscripts/upgrade/pre_upgrade/0000_config.sql changed from smx to svm. for both 3.2 and 3.3 (notice in 3.3 the file only has add_config for 3.3, you need to run it as update_config of course).