> On 5 Jun 2020, at 20:23, Vinícius Ferrão <fer...@versatushpc.com.br> wrote:
> 
> Hi Michal
> 
>> On 5 Jun 2020, at 04:39, Michal Skrivanek <michal.skriva...@redhat.com 
>> <mailto:michal.skriva...@redhat.com>> wrote:
>> 
>> 
>> 
>>> On 5 Jun 2020, at 08:19, Vinícius Ferrão via Users <users@ovirt.org 
>>> <mailto:users@ovirt.org>> wrote:
>>> 
>>> Hello, I’m trying to run ppc64le VM’s on POWER9 but qemu-kvm fails 
>>> complaining about NUMA issues:
>> 
>> that is not a line you should be looking at, it’s just a harmless warning.
>> I suppose it’s the other one, about spectre fixes
>>> 
>>> VM ppc64le.local.versatushpc.com.br 
>>> <http://ppc64le.local.versatushpc.com.br/> is down with error. Exit 
>>> message: internal error: qemu unexpectedly closed the monitor: 
>>> 2020-06-05T06:16:10.716052Z qemu-kvm: warning: CPU(s) not present in any 
>>> NUMA nodes: CPU 4 [core-id: 4], CPU 5 [core-id: 5], CPU 6 [core-id: 6], CPU 
>>> 7 [core-id: 7], CPU 8 [core-id: 8], CPU 9 [core-id: 9], CPU 10 [core-id: 
>>> 10], CPU 11 [core-id: 11], CPU 12 [core-id: 12], CPU 13 [core-id: 13], CPU 
>>> 14 [core-id: 14], CPU 15 [core-id: 15] 2020-06-05T06:16:10.716067Z 
>>> qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA 
>>> config, ability to start up with partial NUMA mappings is obsoleted and 
>>> will be removed in future 2020-06-05T06:16:11.155924Z qemu-kvm: Requested 
>>> safe indirect branch capability level not supported by kvm, try 
>>> cap-ibs=fixed-ibs.
>>> 
>>> Any idea of what’s happening?
>>> 
>>> I found some links, but I’m not sure if they are related or not:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1732726 
>>> <https://bugzilla.redhat.com/show_bug.cgi?id=1732726>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1592648 
>>> <https://bugzilla.redhat.com/show_bug.cgi?id=1592648>
>> yes, they look relevant if that’s the hw you have. We do use 
>> pseries-rhel7.6.0-sxxm machine type in 4.3 (not in 4.4. that would be the 
>> preferred solution, to upgrade).
>> If you don’t care about security you can also modify the machine type per VM 
>> (or in engine db for all VMs) to "pseries-rhel7.6.0"
> 
> I’m using an AC922 machine.

and is it oVirt  4.3 or 4.4?
Bug 1732726 is on RHEL 8, so relevant only for oVirt 4.4, i.e. you’d have to 
have a 4.3 cluster level?
if you really want to keep using -sxxm you need to modify it to add the extra 
flag the bug talks about

this shouldn’t be needed in 4.4 cluster level though

> 
> In fact I can boot the VMs with pseries-rhel7.6.0 but not with 
> pseries-rhel7.6.0-sxxm; how do you made pseries-rhel7.6.0-sxxm works on 4.3 
> release?
> 
> # lscpu
> Architecture:          ppc64le
> Byte Order:            Little Endian
> CPU(s):                128
> On-line CPU(s) list:   0-127
> Thread(s) per core:    4
> Core(s) per socket:    16
> Socket(s):             2
> NUMA node(s):          6
> Model:                 2.2 (pvr 004e 1202)
> Model name:            POWER9, altivec supported
> CPU max MHz:           3800.0000
> CPU min MHz:           2300.0000
> L1d cache:             32K
> L1i cache:             32K
> L2 cache:              512K
> L3 cache:              10240K
> NUMA node0 CPU(s):     0-63
> NUMA node8 CPU(s):     64-127
> NUMA node252 CPU(s):   
> NUMA node253 CPU(s):   
> NUMA node254 CPU(s):   
> NUMA node255 CPU(s): 
> 
> Thank you for helping out.
> 
>> 
>> Thanks,
>> michal
>>> 
>>> Thanks,
>>> 
>>> _______________________________________________
>>> Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
>>> To unsubscribe send an email to users-le...@ovirt.org 
>>> <mailto:users-le...@ovirt.org>
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html 
>>> <https://www.ovirt.org/privacy-policy.html>
>>> oVirt Code of Conduct: 
>>> https://www.ovirt.org/community/about/community-guidelines/ 
>>> <https://www.ovirt.org/community/about/community-guidelines/>
>>> List Archives: 
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/PVVQDBO2XJYBQN7EUDMM74QZJ2UTLRJ2/
>>>  
>>> <https://lists.ovirt.org/archives/list/users@ovirt.org/message/PVVQDBO2XJYBQN7EUDMM74QZJ2UTLRJ2/>

_______________________________________________
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/3GZBCJR4WRPJTQVH6LKIHQEYUMYYYNXI/

Reply via email to