[ovirt-users] Re: EPYC CPU not being detected correctly on cluster
Hi Vinícius,
I am glad you've managed to solve it and thanks for sharing your findings.
Lucia
On Wed, Nov 25, 2020 at 9:07 PM Vinícius Ferrão
wrote:
> Lucia, I ended figuring out.
>
>
>
> The culprit is that I was pinned with the wrong virt module; after running
> this commands I was able to have the CPU properly detected:
>
>
>
> # dnf module reset virt
>
> # dnf module enable virt:8.3
>
> # dnf upgrade –nobest
>
>
>
> I think virt was in 8.2.
>
>
>
> Thank you!
>
>
>
> *From:* Lucia Jelinkova
> *Sent:* Monday, November 23, 2020 6:25 AM
> *To:* Vinícius Ferrão
> *Cc:* users
> *Subject:* Re: [ovirt-users] EPYC CPU not being detected correctly on
> cluster
>
>
>
> Hi Vinícius,
>
>
>
> Thank you for the libvirt output - libvirt marked the EPYC CPU as not
> usable. Let's query qemu why that is. You do not need an oVirt VM to do
> that, just any VM running on qemu, e.g. created by Virtual Machines Manager
> or you can follow the command from the answer here:
>
>
>
>
> https://unix.stackexchange.com/questions/309788/how-to-create-a-vm-from-scratch-with-virsh
>
>
>
> Then you can use the following commands:
>
> sudo virsh list --all
>
> sudo virsh qemu-monitor-command [your-vm's-name] --pretty
> '{"execute":"query-cpu-definitions"}'
>
>
>
> I do not know if this could be related to UEFI Firmware, lets check the
> qemu output first.
>
>
>
> Regards,
>
>
>
> Lucia
>
>
>
>
>
> On Fri, Nov 20, 2020 at 4:07 PM Vinícius Ferrão
> wrote:
>
> Hi Lucia,
>
>
>
> I had to create an user for virsh:
>
> # saslpasswd2 -a libvirt test
>
> Password:
>
> Again (for verification):
>
>
>
> With that in mind, here’s the outputs:
>
>
>
>
>
> /usr/libexec/qemu-kvm
>
> kvm
>
> pc-i440fx-rhel7.6.0
>
> x86_64
>
>
>
>
>
>
>
>
>
>
>
> /usr/share/OVMF/OVMF_CODE.secboot.fd
>
>
>
> rom
>
> pflash
>
>
>
>
>
> yes
>
> no
>
>
>
>
>
> no
>
>
>
>
>
>
>
>
>
>
>
>
>
> EPYC-IBPB
>
> AMD
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> qemu64
>
> qemu32
>
> phenom
>
> pentium3
>
> pentium2
>
> pentium
>
> n270
>
> kvm64
>
> kvm32
>
> coreduo
>
> core2duo
>
> athlon
>
> Westmere-IBRS
>
> Westmere
>
> Skylake-Server-noTSX-IBRS
>
> Skylake-Server-IBRS
>
> Skylake-Server
>
> Skylake-Client-noTSX-IBRS
>
> Skylake-Client-IBRS
>
> Skylake-Client
>
> SandyBridge-IBRS
>
> SandyBridge
>
> Penryn
>
> Opteron_G5
>
> Opteron_G4
>
> Opteron_G3
>
> Opteron_G2
>
> Opteron_G1
>
> Nehalem-IBRS
>
> Nehalem
>
> IvyBridge-IBRS
>
> IvyBridge
>
> Icelake-Server-noTSX
>
> Icelake-Server
>
> Icelake-Client-noTSX
>
> Icelake-Client
>
> Haswell-noTSX-IBRS
>
> Haswell-noTSX
>
> Haswell-IBRS
>
> Haswell
>
> EPYC-IBPB
>
> EPYC
>
> Dhyana
>
> Cooperlake
>
> Conroe
>
> Cascadelake-Server-noTSX
>
> Cascadelake-Server
>
> Broadwell-noTSX-IBRS
>
> Broadwell-noTSX
>
> Broadwell-IBRS
>
> Broadwell
>
> 486
>
>
>
>
>
>
>
>
>
>
>
> disk
>
> cdrom
>
> floppy
>
> lun
>
>
>
>
>
> ide
>
> fdc
>
> scsi
>
> virtio
>
> usb
>
> sata
>
>
>
>
>
> virtio
>
> virtio-transitional
>
> virtio-non-transitional
>
>
>
>
>
>
>
>
>
> sdl
>
[ovirt-users] Re: EPYC CPU not being detected correctly on cluster
Lucia, I ended figuring out.
The culprit is that I was pinned with the wrong virt module; after running this
commands I was able to have the CPU properly detected:
# dnf module reset virt
# dnf module enable virt:8.3
# dnf upgrade –nobest
I think virt was in 8.2.
Thank you!
From: Lucia Jelinkova
Sent: Monday, November 23, 2020 6:25 AM
To: Vinícius Ferrão
Cc: users
Subject: Re: [ovirt-users] EPYC CPU not being detected correctly on cluster
Hi Vinícius,
Thank you for the libvirt output - libvirt marked the EPYC CPU as not usable.
Let's query qemu why that is. You do not need an oVirt VM to do that, just any
VM running on qemu, e.g. created by Virtual Machines Manager or you can follow
the command from the answer here:
https://unix.stackexchange.com/questions/309788/how-to-create-a-vm-from-scratch-with-virsh
Then you can use the following commands:
sudo virsh list --all
sudo virsh qemu-monitor-command [your-vm's-name] --pretty
'{"execute":"query-cpu-definitions"}'
I do not know if this could be related to UEFI Firmware, lets check the qemu
output first.
Regards,
Lucia
On Fri, Nov 20, 2020 at 4:07 PM Vinícius Ferrão
mailto:fer...@versatushpc.com.br>> wrote:
Hi Lucia,
I had to create an user for virsh:
# saslpasswd2 -a libvirt test
Password:
Again (for verification):
With that in mind, here’s the outputs:
/usr/libexec/qemu-kvm
kvm
pc-i440fx-rhel7.6.0
x86_64
/usr/share/OVMF/OVMF_CODE.secboot.fd
rom
pflash
yes
no
no
EPYC-IBPB
AMD
qemu64
qemu32
phenom
pentium3
pentium2
pentium
n270
kvm64
kvm32
coreduo
core2duo
athlon
Westmere-IBRS
Westmere
Skylake-Server-noTSX-IBRS
Skylake-Server-IBRS
Skylake-Server
Skylake-Client-noTSX-IBRS
Skylake-Client-IBRS
Skylake-Client
SandyBridge-IBRS
SandyBridge
Penryn
Opteron_G5
Opteron_G4
Opteron_G3
Opteron_G2
Opteron_G1
Nehalem-IBRS
Nehalem
IvyBridge-IBRS
IvyBridge
Icelake-Server-noTSX
Icelake-Server
Icelake-Client-noTSX
Icelake-Client
Haswell-noTSX-IBRS
Haswell-noTSX
Haswell-IBRS
Haswell
EPYC-IBPB
EPYC
Dhyana
Cooperlake
Conroe
Cascadelake-Server-noTSX
Cascadelake-Server
Broadwell-noTSX-IBRS
Broadwell-noTSX
Broadwell-IBRS
Broadwell
486
disk
cdrom
floppy
lun
ide
fdc
scsi
virtio
usb
sata
virtio
virtio-transitional
virtio-non-transitional
sdl
vnc
spice
vga
cirrus
qxl
virtio
none
bochs
ramfb
subsystem
default
mandatory
requisite
optional
usb
pci
scsi
default
vfio
virtio
virtio-transitional
virtio-non-transitional
random
egd
47
1
Regarding the last two commands, I don’t have any VM running, since I cannot
start anything on the engine.
I’m starting to suspect that this may be something in the UEFI Firmware.
Any thoughts?
Thanks,
From: Lucia Jelinkova mailto:ljeli...@redhat.com>>
Sent: Friday, November 20, 2020 5:30 AM
To: Vinícius Ferrão
mailto:fer...@versatushpc.com.br>>
Cc: users mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] EPYC CPU not being detected correctly on cluster
Hi,
oVirt CPU detection depends on libvirt (and that depends on qemu) CPU models.
Could you please run the following command to see what libvirt reports?
virsh domcapabilities
That should give you the list of CPUs known to libvirt with a usability flag
for each CPU.
If you find out that the CPU is not usable by libvirt, you might want to dig
deeper by querying quemu directly.
Locate any VM running on the system by
sudo virsh list --all
Use the name of a VM in the following command:
sudo virsh qemu-monitor-command [your-vm's-name] --pretty
'{"execute":"query-cpu-definitions"}'
That would give you the list of all CPUs supported by qemu and it will list all
cpu's features that are not available on your system.
Regards,
Lucia
On Thu, Nov 19, 2020 at 9:38 PM Vinícius Ferrão via Users
mailto:users@ovirt.
[ovirt-users] Re: EPYC CPU not being detected correctly on cluster
Hi Vinícius,
Thank you for the libvirt output - libvirt marked the EPYC CPU as not
usable. Let's query qemu why that is. You do not need an oVirt VM to do
that, just any VM running on qemu, e.g. created by Virtual Machines Manager
or you can follow the command from the answer here:
https://unix.stackexchange.com/questions/309788/how-to-create-a-vm-from-scratch-with-virsh
Then you can use the following commands:
sudo virsh list --all
sudo virsh qemu-monitor-command [your-vm's-name] --pretty
'{"execute":"query-cpu-definitions"}'
I do not know if this could be related to UEFI Firmware, lets check the
qemu output first.
Regards,
Lucia
On Fri, Nov 20, 2020 at 4:07 PM Vinícius Ferrão
wrote:
> Hi Lucia,
>
>
>
> I had to create an user for virsh:
>
> # saslpasswd2 -a libvirt test
>
> Password:
>
> Again (for verification):
>
>
>
> With that in mind, here’s the outputs:
>
>
>
>
>
> /usr/libexec/qemu-kvm
>
> kvm
>
> pc-i440fx-rhel7.6.0
>
> x86_64
>
>
>
>
>
>
>
>
>
>
>
> /usr/share/OVMF/OVMF_CODE.secboot.fd
>
>
>
> rom
>
> pflash
>
>
>
>
>
> yes
>
> no
>
>
>
>
>
> no
>
>
>
>
>
>
>
>
>
>
>
>
>
> EPYC-IBPB
>
> AMD
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> qemu64
>
> qemu32
>
> phenom
>
> pentium3
>
> pentium2
>
> pentium
>
> n270
>
> kvm64
>
> kvm32
>
> coreduo
>
> core2duo
>
> athlon
>
> Westmere-IBRS
>
> Westmere
>
> Skylake-Server-noTSX-IBRS
>
> Skylake-Server-IBRS
>
> Skylake-Server
>
> Skylake-Client-noTSX-IBRS
>
> Skylake-Client-IBRS
>
> Skylake-Client
>
> SandyBridge-IBRS
>
> SandyBridge
>
> Penryn
>
> Opteron_G5
>
> Opteron_G4
>
> Opteron_G3
>
> Opteron_G2
>
> Opteron_G1
>
> Nehalem-IBRS
>
> Nehalem
>
> IvyBridge-IBRS
>
> IvyBridge
>
> Icelake-Server-noTSX
>
> Icelake-Server
>
> Icelake-Client-noTSX
>
> Icelake-Client
>
> Haswell-noTSX-IBRS
>
> Haswell-noTSX
>
> Haswell-IBRS
>
> Haswell
>
> EPYC-IBPB
>
> EPYC
>
> Dhyana
>
> Cooperlake
>
> Conroe
>
> Cascadelake-Server-noTSX
>
> Cascadelake-Server
>
> Broadwell-noTSX-IBRS
>
> Broadwell-noTSX
>
> Broadwell-IBRS
>
> Broadwell
>
> 486
>
>
>
>
>
>
>
>
>
>
>
> disk
>
> cdrom
>
> floppy
>
> lun
>
>
>
>
>
> ide
>
> fdc
>
> scsi
>
> virtio
>
> usb
>
> sata
>
>
>
>
>
> virtio
>
> virtio-transitional
>
> virtio-non-transitional
>
>
>
>
>
>
>
>
>
> sdl
>
> vnc
>
> spice
>
>
>
>
>
>
>
>
>
> vga
>
> cirrus
>
> qxl
>
> virtio
>
> none
>
> bochs
>
> ramfb
>
>
>
>
>
>
>
>
>
> subsystem
>
>
>
>
>
> default
>
> mandatory
>
> requisite
>
> optional
>
>
>
>
>
> usb
>
> pci
>
> scsi
>
>
>
>
>
>
>
> default
>
> vfio
>
>
>
>
>
>
>
>
>
> virtio
>
> virtio-transitional
>
> virtio-non-transitional
>
>
>
>
>
> random
>
> egd
>
>
>
>
[ovirt-users] Re: EPYC CPU not being detected correctly on cluster
Hi Lucia,
I had to create an user for virsh:
# saslpasswd2 -a libvirt test
Password:
Again (for verification):
With that in mind, here’s the outputs:
/usr/libexec/qemu-kvm
kvm
pc-i440fx-rhel7.6.0
x86_64
/usr/share/OVMF/OVMF_CODE.secboot.fd
rom
pflash
yes
no
no
EPYC-IBPB
AMD
qemu64
qemu32
phenom
pentium3
pentium2
pentium
n270
kvm64
kvm32
coreduo
core2duo
athlon
Westmere-IBRS
Westmere
Skylake-Server-noTSX-IBRS
Skylake-Server-IBRS
Skylake-Server
Skylake-Client-noTSX-IBRS
Skylake-Client-IBRS
Skylake-Client
SandyBridge-IBRS
SandyBridge
Penryn
Opteron_G5
Opteron_G4
Opteron_G3
Opteron_G2
Opteron_G1
Nehalem-IBRS
Nehalem
IvyBridge-IBRS
IvyBridge
Icelake-Server-noTSX
Icelake-Server
Icelake-Client-noTSX
Icelake-Client
Haswell-noTSX-IBRS
Haswell-noTSX
Haswell-IBRS
Haswell
EPYC-IBPB
EPYC
Dhyana
Cooperlake
Conroe
Cascadelake-Server-noTSX
Cascadelake-Server
Broadwell-noTSX-IBRS
Broadwell-noTSX
Broadwell-IBRS
Broadwell
486
disk
cdrom
floppy
lun
ide
fdc
scsi
virtio
usb
sata
virtio
virtio-transitional
virtio-non-transitional
sdl
vnc
spice
vga
cirrus
qxl
virtio
none
bochs
ramfb
subsystem
default
mandatory
requisite
optional
usb
pci
scsi
default
vfio
virtio
virtio-transitional
virtio-non-transitional
random
egd
47
1
Regarding the last two commands, I don’t have any VM running, since I cannot
start anything on the engine.
I’m starting to suspect that this may be something in the UEFI Firmware.
Any thoughts?
Thanks,
From: Lucia Jelinkova
Sent: Friday, November 20, 2020 5:30 AM
To: Vinícius Ferrão
Cc: users
Subject: Re: [ovirt-users] EPYC CPU not being detected correctly on cluster
Hi,
oVirt CPU detection depends on libvirt (and that depends on qemu) CPU models.
Could you please run the following command to see what libvirt reports?
virsh domcapabilities
That should give you the list of CPUs known to libvirt with a usability flag
for each CPU.
If you find out that the CPU is not usable by libvirt, you might want to dig
deeper by querying quemu directly.
Locate any VM running on the system by
sudo virsh list --all
Use the name of a VM in the following command:
sudo virsh qemu-monitor-command [your-vm's-name] --pretty
'{"execute":"query-cpu-definitions"}'
That would give you the list of all CPUs supported by qemu and it will list all
cpu's features that are not available on your system.
Regards,
Lucia
On Thu, Nov 19, 2020 at 9:38 PM Vinícius Ferrão via Users
mailto:users@ovirt.org>> wrote:
Hi
I’ve an strange issue with two hosts (not using the hypervisor image) with EPYC
CPUs, on the engine I got this message:
The host CPU does not match the Cluster CPU Type and is running in a degraded
mode. It is missing the following CPU flags: model_EPYC. Please update the host
CPU microcode or change the Cluster CPU Type.
But it is an EPYC CPU, the firmware is updated to the latest versions, but for
some reason oVirt does not like it.
Here’s the relevant output from VDSM:
"cpuCores": "128",
"cpuFlags":
"ibs,vme,abm,sep,ssse3,perfctr_core,sse4_2,skip-l1dfl-vmentry,cx16,pae,misalignsse,avx2,smap,movbe,vgif,rdctl-no,extapic,clflushopt,de,sse4_1,xsaveerptr,perfctr_llc,fma,mca,sse,rdtscp,monitor,umip,mwaitx,cr8_legacy,mtrr,stibp,bmi2,pclmulqdq,amd-ssbd,lbrv,pdpe1gb,constant_tsc,vmmcall,f16c,ibrs,fsgsbase,invtsc,nopl,lm,3dnowprefetch,smca,ht,tsc_adjust,popcnt,cpb,bmi1,mmx,arat,aperfmperf,bpext,cqm_occup_llc,virt-ssbd,tce,pse,xsave,xgetbv1,topoext,sha_ni,amd_ppin,rdrand,cpuid,tsc_scale,extd_apicid,cqm,rep_good,tsc,sse4a,flushbyasid,pschange-mc-no,mds-no,ibpb,smep,clflush,tsc-deadline,fxsr,pat,avx,pfthreshold,v_vmsave_vmload,osvw,xsavec,cdp_l3,clzero,svm_lock,nonstop_tsc,adx,hw_pstate,spec-ctrl,arch-capabilities,xsaveopt,skinit,rdt_a,svm,rdpid,lah
[ovirt-users] Re: EPYC CPU not being detected correctly on cluster
Hi,
oVirt CPU detection depends on libvirt (and that depends on qemu) CPU
models. Could you please run the following command to see what libvirt
reports?
virsh domcapabilities
That should give you the list of CPUs known to libvirt with a usability
flag for each CPU.
If you find out that the CPU is not usable by libvirt, you might want to
dig deeper by querying quemu directly.
Locate any VM running on the system by
sudo virsh list --all
Use the name of a VM in the following command:
sudo virsh qemu-monitor-command [your-vm's-name] --pretty
'{"execute":"query-cpu-definitions"}'
That would give you the list of all CPUs supported by qemu and it will list
all cpu's features that are not available on your system.
Regards,
Lucia
On Thu, Nov 19, 2020 at 9:38 PM Vinícius Ferrão via Users
wrote:
> Hi
>
>
>
> I’ve an strange issue with two hosts (not using the hypervisor image) with
> EPYC CPUs, on the engine I got this message:
>
>
>
> The host CPU does not match the Cluster CPU Type and is running in a
> degraded mode. It is missing the following CPU flags: model_EPYC. Please
> update the host CPU microcode or change the Cluster CPU Type.
>
>
>
> But it is an EPYC CPU, the firmware is updated to the latest versions, but
> for some reason oVirt does not like it.
>
>
>
> Here’s the relevant output from VDSM:
>
> "cpuCores": "128",
>
> "cpuFlags":
> "ibs,vme,abm,sep,ssse3,perfctr_core,sse4_2,skip-l1dfl-vmentry,cx16,pae,misalignsse,avx2,smap,movbe,vgif,rdctl-no,extapic,clflushopt,de,sse4_1,xsaveerptr,perfctr_llc,fma,mca,sse,rdtscp,monitor,umip,mwaitx,cr8_legacy,mtrr,stibp,bmi2,pclmulqdq,amd-ssbd,lbrv,pdpe1gb,constant_tsc,vmmcall,f16c,ibrs,fsgsbase,invtsc,nopl,lm,3dnowprefetch,smca,ht,tsc_adjust,popcnt,cpb,bmi1,mmx,arat,aperfmperf,bpext,cqm_occup_llc,virt-ssbd,tce,pse,xsave,xgetbv1,topoext,sha_ni,amd_ppin,rdrand,cpuid,tsc_scale,extd_apicid,cqm,rep_good,tsc,sse4a,flushbyasid,pschange-mc-no,mds-no,ibpb,smep,clflush,tsc-deadline,fxsr,pat,avx,pfthreshold,v_vmsave_vmload,osvw,xsavec,cdp_l3,clzero,svm_lock,nonstop_tsc,adx,hw_pstate,spec-ctrl,arch-capabilities,xsaveopt,skinit,rdt_a,svm,rdpid,lahf_lm,fpu,rdseed,fxsr_opt,sse2,nrip_save,vmcb_clean,sme,cat_l3,cqm_mbm_local,irperf,overflow_recov,avic,mce,mmxext,msr,cx8,hypervisor,wdt,mba,nx,decodeassists,cmp_legacy,x2apic,perfctr_nb,succor,pni,xsaves,clwb,cqm_llc,syscall,apic,pge,npt,pse36,cmov,ssbd,pausefilter,sev,aes,wbnoinvd,cqm_mbm_total,spec_ctrl,model_qemu32,model_Opteron_G3,model_Nehalem-IBRS,model_qemu64,model_Conroe,model_kvm64,model_Penryn,model_SandyBridge,model_pentium,model_pentium2,model_kvm32,model_Nehalem,model_Opteron_G2,model_pentium3,model_Opteron_G1,model_SandyBridge-IBRS,model_486,model_Westmere-IBRS,model_Westmere",
>
> "cpuModel": "AMD EPYC 7H12 64-Core Processor",
>
> "cpuSockets": "2",
>
> "cpuSpeed": "3293.405",
>
> "cpuThreads": "256",
>
>
>
> Any ideia on why ou what to do to fix it?
>
>
>
> Thanks,
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WP6XL6ODTLJVB46MAXKCOA34PEFN576Q/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OOLJHQDNC4KY4O4B3SJ3PORDKQU6BQM7/
