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
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:
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:
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
Do you have any documentation or compatibility matrix between oVirt and
processors?
How can I know if a processor is compatible?
I ask because in the *lscpu* command I see 2 sockets, but in the *engine* I
only see 1 socket.
BR.
--
Att,
Jorge Visentini
+55 55 98432-9868
Hello.
Found your solution very useful. Thank you.
Have some questions.
1. Is there a way to pass virtual machine name as an argument to yml script?
2. Also there is a situation, when script unable to delete older backups of VM,
if that VM excluded from vmlist for the next backup (syntax err:
6 matches
Mail list logo
