CPU flags reported by beaker-system-scan with lshw: [u'apic', u'clflush', u'cmov', u'cx16', u'cx8', u'de', u'fpu', u'fpu_exception', u'fxsr', u'hypervisor', u'lahf_lm', u'mca', u'mce', u'mmx', u'msr', u'mtrr', u'nx', u'pae', u'pge', u'pni', u'pse', u'pse36', u'sse', u'sse2', u'syscall', u'tsc', u'unfair_spinlock', u'wp', u'x86-64'] 'lm' is missing, 'x86-64' and 'fpu_exception' are extra. Neither of these two appear in flags: field of /proc/cpuinfo therefore we need to determine if they are desirable or not. Reproducible on any x86_64 system, including KVM guests.
lm - lshw explicitly renames "lm" capability to "x86-64" solution: We could just replace x86-64 by lm in beaker-system-scan wp - https://forums.gentoo.org/viewtopic-t-89406-view-previous.html?sid=43c68f2c7bff03de97d0c8de7ae1f386 cpufreq - lshw lists "cpufreq" as a capability when it finds the file "/sys/devices/system/cpu/cpu%d/cpufreq/" (https://wiki.archlinux.org/index.php/CPU_frequency_scaling) solution: I think having the last two as flags doesn't make a lot of sense. But then having them doesn't cause any harm i believe.
(In reply to Amit Saha from comment #3) Sounds good, let's rename x86-64 to lm and keep wp and cpufreq.
http://gerrit.beaker-project.org/#/c/4185/
Verification instructions: 1. Reserve a x86_64 box with RHEL 7 2. Install beaker-system-scan using "yum install beaker-system-scan" 3. Run, "beaker-system-scan -d" See that lm is present in the CpuFlags output: {'Arch': ['x86_64'], 'Cpu': {'CpuFlags': ['lm', .. }
Beaker 21.0 has been released.