[ovirt-users] [HEADS UP] CentOS 7.3 is rolling out, need qemu-kvm-ev 2.6

[Gianluca Cecchi]

On Tue, Dec 13, 2016 at 12:29 PM, Paolo Bonzini <pbonzini at redhat.com> wrote:

>
>
> On 12/12/2016 15:06, Sandro Bonazzola wrote:
> >
> >     Hello,
> >     where to find details about this info?
> >     I ask because on my tests in a nested environment with 4.1 beta on
> >     CentOS 7.2 + CR (that should match upcoming 7.3) I was not able to
> >     power on the SHE VM using qemu-kvm-ev-2.6.0-27.1.el7.x86_64.rpm
> >     manually downloaded
> >     by http://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common
> >     <http://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common>
> >
> >     Got error
> >     warning: host doesn't support requested feature: CPUID.07H:EBX.erms
> >     [bit 9]
> >
> >
> > Michal, Paolo, what about above error?
>
> It's harmless.  I would first of all check if L0 has the bit (you can do
> it with cat /proc/cpuinfo on a live Linux CD).  If it does, tell VMWare
> to fix it.  If it bugs you, you can force the bit to 1 in ESX, even if
> L0 doesn't have it.
>
> Paolo
>


Hello,
thanks for answering.
On an identical nuc where I have instead oVirt 4.0.5 directly installed on
L0 host with CentOS 7.2 I get:

[g.cecchi at ovirt01 ~]$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 78
model name : Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz
stepping : 3
microcode : 0x8a
cpu MHz : 2740.570
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est
tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida
arat epb pln pts dtherm hwp hwp_noitfy hwp_act_window hwp_epp tpr_shadow
vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms
invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves
bogomips : 3600.06
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

. . .

What is the flag to check?
Even if harmless, it seems that qemu-2.6 doesn't boot the self hosted
engine VM, because it remains somehow inside a sort of bios window, while
qemu-2.3 boots it without any problem and able to configure hosted engine...
Gianluca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20161213/77f19ebc/attachment-0001.html>