[ovirt-users] Re: Processors compatibility matrix oVirt

2023-07-21 Thread jorgevisentini
Just to document it and keep history. I solved the problem by updating the kernel and libvirt. Kernel-4.x and libvirt-8.x do not correctly detect processors from the cascadelake family. If you have 2 physical sockets on the host, the combination of kernel and libvirt above will only detect 1

[ovirt-users] Re: Processors compatibility matrix oVirt

2023-06-28 Thread Jorge Visentini
of lscpu) > > "cpuSockets": "1", > > Fault: "cpuSockets": "1" and not "cpuSockets": "2" > > However "cpuThreads": "112" and list in "onlineCpus": is correct. > > > > > > BR, >

[ovirt-users] Re: Processors compatibility matrix oVirt

2023-06-28 Thread Volenbovskyi, Konstantin
ntin Von: Jorge Visentini Datum: Mittwoch, 28. Juni 2023 um 15:37 An: "Volenbovskyi, Konstantin" Cc: Dean L , "users@ovirt.org" Betreff: Re: [ovirt-users] Re: Processors compatibility matrix oVirt Hi, Konstantin. Thank you for the fast reply. On oVirt... New Virtual Machi

[ovirt-users] Re: Processors compatibility matrix oVirt

2023-06-28 Thread Jorge Visentini
t; > virsh capabilities > > > > and possibly see the issue? > > By the way most likely I think you will see *CPU socket(s): 1* in > virsh nodeinfo, but with *NUMA cell(s):2* > > (that will be OK) > > > > BR, > > Konstantin > > > > *V

[ovirt-users] Re: Processors compatibility matrix oVirt

2023-06-28 Thread Volenbovskyi, Konstantin
Datum: Dienstag, 27. Juni 2023 um 18:50 An: Dean L Cc: "users@ovirt.org" Betreff: [ovirt-users] Re: Processors compatibility matrix oVirt Sorry, I mentioned it wrong. The engine VM is ok. What happens is that the lscpu output of the physical host is different from the host information

[ovirt-users] Re: Processors compatibility matrix oVirt

2023-06-27 Thread Jorge Visentini
Sorry, I mentioned it wrong. The engine VM is ok. What happens is that the lscpu output of the physical host is different from the host information in oVirt. *lscpu:* CPU(s): 112 On-line CPU(s) list: 0-111 Thread(s) per core: 2 Core(s) per socket: 28 *Socket(s): 2* NUMA

[ovirt-users] Re: Processors compatibility matrix oVirt

2023-06-27 Thread Jorge Visentini
Mencionei errado, não me refiro à VM da engine, me refiro ao oVirt como um todo. No host mostra apenas 1 socket. *lscpu:* CPU(s): 112 On-line CPU(s) list: 0-111 Thread(s) per core: 2 Core(s) per socket: 28 *Socket(s): 2* NUMA node(s):2 Vendor ID:

[ovirt-users] Re: Processors compatibility matrix oVirt

2023-06-27 Thread Dean L via Users
Jorge, Your 8276 processor belongs to the former Cascade Lake Family (server), which is supported by oVirt (listed as Intel Cascadelake Server Family). For CPU requirements see:

[ovirt-users] Re: Processors compatibility matrix oVirt

2023-06-27 Thread Douglas Oliveira
Olá Jorge Se foi alocado apenas um socket a vm hosted engine, ela verá exatamente essa configuração. Em ter., 27 de jun. de 2023 10:45, Jorge Visentini escreveu: > Do you have any documentation or compatibility matrix between oVirt and > processors? > How can I know if a processor is