subject:"\[ovirt\-users\] Re\: Wrong CPU\?"

[ovirt-users] Re: Wrong CPU type recognized on a new Pentium G4560 Kaby Lake

2020-04-28 Thread Sandro Bonazzola

Il giorno mar 28 apr 2020 alle ore 10:09  ha scritto:

> Hi,
> I installed an ovirt node based on latest 4.3.9 iso on this hardware:
>
> CPU Intel Pentium G4560
> Motherboard Asus P10S-i C232 Chipset
>
> Overall setup has no problem but I noticed that the CPU type is recognized
> as:
>
> Intel Westmere IBRS SSBD MDS Family
>

+Ryan Barry  can you please have a look at this?



>
> The overall system info are:
>
> OS Version:
> RHEL - 7 - 7.1908.0.el7.centos
> OS Description:
> oVirt Node 4.3.9
> Kernel Version:
> 3.10.0 - 1062.18.1.el7.x86_64
> KVM Version:
> 2.12.0 - 33.1.el7_7.4
> LIBVIRT Version:
> libvirt-4.5.0-23.el7_7.6
> VDSM Version:
> vdsm-4.30.43-1.el7
> SPICE Version:
> 0.14.0 - 7.el7
> GlusterFS Version:
> glusterfs-6.8-1.el7
> CEPH Version:
> librbd1-10.2.5-4.el7
> Open vSwitch Version:
> openvswitch-2.11.0-4.el7
> Kernel Features:
> PTI: 1, IBRS: 0, RETP: 1, SSBD: 3
> VNC Encryption:
> Disabled
>
> Thats give me some problem on the cluster since I'm trying to join some
> notebooks to it(it's only a lab) and they are recognized ad Haswell CPUs,
> making them too new to be joined
>
> Any help on this?
>
> 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/XC6UVUFBOYL2A5PR6KPR2YXYIIB3CHVX/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA 

sbona...@redhat.com
*
*
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.
*
___
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/WV7UPT6TBOJKPO4FWRXQVQOO2R7BQU5N/

[ovirt-users] Re: Wrong CPU?

2019-11-19 Thread Juhani Rautiainen

Hi!

Had to get back to work to check which CPU we had. We have AMD Epyc
7281 and ovirt CPU Type is AMD EPYC IBPB SSBD. It seems that your CPU
is the next generation (Zen2) and I'm pretty sure that problem is with
Qemu version. As far as I can see from git there is not even Zen2
support in latest Qemu (checking by target/i386/cpu.c)? I mean they
added Hygon Dhyana (never even heard about this chinese AMD EPYC
clone) and in that discussion there was reference to Zen2
architecture. So biggest problem for oVirt seems to come from
upstream. I mean that Zen2 is quite good for virtualization and it's
going to sell a lot. Maybe AMD should help with that push?

-Juhani

On Fri, Nov 15, 2019 at 9:03 PM Christian Reiss
 wrote:
>
> Sorry,
>
> I meant EPYC, not Ryzen.
> How did you solve your EPYC issue?
>
> -Chris.
>
> On 15/11/2019 18:55, Juhani Rautiainen wrote:
> > Hi!
> >
> > It might be that the Qemu in oVirt doesn't recognize the Ryzen. That
> > was case with Epyc when I started using oVirt. It was reconized as a
> > Opteron G2 which caused lot's of problems when upgrading to 4.3.
> >
> > -Juhani
> >
> > On Fri, Nov 15, 2019 at 6:45 PM Christian Reiss
> >  wrote:
> >>
> >> Hey folks,
> >>
> >> running an AMD Ryzen CPU here:
> >>
> >> processor   : 0
> >> vendor_id   : AuthenticAMD
> >> cpu family  : 23
> >> model   : 49
> >> model name  : AMD EPYC 7282 16-Core Processor
> >>
> >> However, libvirt is detecting this as EPYC-IBPB without the ssbd flags?
> >>
> >>   
> >> x86_64
> >> EPYC-IBPB
> >> AMD
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >>   
> >>
> >>
> >> [root@node01 ~]# grep ssbd /var/cache/libvirt/qemu/capabilities/*.xml
> >>   
> >>   
> >>   
> >>   
> >>
> >> But the flag is there:
> >>
> >> [root@node01 ~]# grep ssbd /proc/cpuinfo | tail -n1
> >> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
> >> cmov
> >> pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
> >> pdpe1gb rdtscp lm constant_tsc art rep_good nopl xtopology nonstop_tsc
> >> extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16
> >> sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy
> >> svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs
> >> skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb
> >> cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall
> >> fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb
> >> sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total
> >> cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save
> >> tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
> >> avic v_vmsave_vmload vgif umip overflow_recov succor smca
> >>
> >> I tried adding "options kvm_amd avic=1" as well as "options kvm_amd
> >> avic=0" to /etc/modprobe.d/kvm.conf (always with reboots), adding
> >> mitigations=off to grub.. I can't think of any other solution.
> >>
> >> I just can't get the oVirt engine running with the ssbd flag. Seems cpu
> >> can do this, oVirt can do this, libvirt does not detect the cpu
> >> correctly or at least ignores it. But the hosted engine demands it.
> >>
> >> I am at a loss. Any help is oh-so-greatly appreciated.
> >>
> >> -Chris.
> >>
> >> --
> >>Christian Reiss - em...@christian-reiss.de /"\  ASCII Ribbon
> >>  supp...@alpha-labs.net   \ /Campaign
> >>X   against HTML
> >>WEB alpha-labs.net / \   in eMails
> >>
> >>GPG Retrieval https://gpg.christian-reiss.de
> >>GPG ID ABCD43C5, 0x44E29126ABCD43C5
> >>GPG fingerprint = 9549 F537 2596 86BA 733C  A4ED 44E2 9126 ABCD 43C5
> >>
> >>"It's better to reign in hell than to serve in heaven.",
> >> John Milton, Paradise lost.
> >> ___
> >> Users mailing list -- users@ovirt.org
> >> To unsubscribe send an email to users-le...@ovirt.org
> >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> >> oVirt Code of Conduct: 
> >> https://www.ovirt.org/community/about/community-guidelines/
> >> List Archives: 
> >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/PPXT55FJZESYOAOPR7HY5LOHTYELWDN6/
> >
> >
> >
>
> --
>   Christian Reiss - em...@christian-reiss.de /"\  ASCII Ribbon
> supp...@alpha-labs.net   \ /Campaign
>   X   against HTML
>   WEB alpha-labs.net

[ovirt-users] Re: Wrong CPU?

2019-11-19 Thread Christian Reiss

Hey Michal,

thanks for replying.
First off and in answer to most of your questions: No clue. Wasn't me.

On 19/11/2019 09:32, Michal Skrivanek wrote:

I’m curious why do you need virt-ssbd for hosted engine? What for?

I don't. Deploying the oVirt hosted engine on the hyperconverged cluster
enables the flag in the ovirt engine by default. I _wish_ it would not
be there/ do that.

yes, AFAIK Zen2 is not yet supported in upstream. Once it is we’ll pick
it up afterwards.
But it doesn’t mean you can’t use it for running stuff in EPYC or lower
CPU family feature set.

But without an oVirt hosted engine, that won't install due to CPU flags,
how can I change CPU flags? :)

in 4.3 we still use flags instead of libvirt feature detection (which
we’re fixing in 4.4, but so far it’s playing to your advantage:)
So seeing “ssbd" below in cpuinfo should be enough to detect the oVirt
type with SSBD. Where exatly you see that not working?

Doing: Installing fresh 3-Server cluster from oVirt Node installer.
Doing HCI oVirt engine without any modifications.

Expected result: oVirt engine running.

Actual result: Nothing is starting due to cpu flags, ssbd is among those
errors.

So this is what I would define as "not seeing working". Also not seeing
my advantage here: Not working is not working, really ;)

I could happily live a great live if the cluster would _somehow_ just
work. It just does not. If there would be an option to disable/enable
ssbd (whatever just works) and oVirt engine can be installed and a VM
would run I would be so happy.

Cheers,
Chris.

--
Christian Reiss - em...@christian-reiss.de /"\ ASCII Ribbon
supp...@alpha-labs.net \ /Campaign
X against HTML
WEB alpha-labs.net / \ in eMails

GPG Retrieval https://gpg.christian-reiss.de
GPG ID ABCD43C5, 0x44E29126ABCD43C5
GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5

"It's better to reign in hell than to serve in heaven.",
John Milton, Paradise lost.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AYH2WCD6HC2PCTEDSXRD7NPQG7IIN7U3/

[ovirt-users] Re: Wrong CPU?

2019-11-19 Thread Michal Skrivanek



> On 18 Nov 2019, at 09:29, Christian Reiss  wrote:
> 
> Ugh,
> 
> first off thanks for all your effort and information. Much obliged.
> But this also means that I am looking at a lng time before I can go to 
> production with this cluster. Now I am sad.
> 
> Would it be an option to run the engine on dedicated hardware and control the 
> cluster from there? Or is that thing in total not usable?

I’m curious why do you need virt-ssbd for hosted engine? What for? 

> 
> -Chris.
> 
> On 18/11/2019 07:25, Juhani Rautiainen wrote:
>> Hi!
>> Had to get back to work to check which CPU we had. We have AMD Epyc
>> 7281 and ovirt CPU Type is AMD EPYC IBPB SSBD. It seems that your CPU
>> is the next generation (Zen2) and I'm pretty sure that problem is with
>> Qemu version. As far as I can see from git there is not even Zen2

yes, AFAIK Zen2 is not yet supported in upstream. Once it is we’ll pick it up 
afterwards.
But it doesn’t mean you can’t use it for running stuff in EPYC or lower CPU 
family feature set.


>> support in latest Qemu (checking by target/i386/cpu.c)? I mean they
>> added Hygon Dhyana (never even heard about this chinese AMD EPYC
>> clone) and in that discussion there was reference to Zen2
>> architecture. So biggest problem for oVirt seems to come from
>> upstream. I mean that Zen2 is quite good for virtualization and it's
>> going to sell a lot. Maybe AMD should help with that push?
>> -Juhani
>> On Fri, Nov 15, 2019 at 9:03 PM Christian Reiss
>> mailto:em...@christian-reiss.de>> wrote:
>>> 
>>> Sorry,
>>> 
>>> I meant EPYC, not Ryzen.
>>> How did you solve your EPYC issue?
>>> 
>>> -Chris.
>>> 
>>> On 15/11/2019 18:55, Juhani Rautiainen wrote:
 Hi!
 
 It might be that the Qemu in oVirt doesn't recognize the Ryzen. That
 was case with Epyc when I started using oVirt. It was reconized as a
 Opteron G2 which caused lot's of problems when upgrading to 4.3.
 
 -Juhani
 
 On Fri, Nov 15, 2019 at 6:45 PM Christian Reiss
  wrote:
> 
> Hey folks,
> 
> running an AMD Ryzen CPU here:
> 
> processor   : 0
> vendor_id   : AuthenticAMD
> cpu family  : 23
> model   : 49
> model name  : AMD EPYC 7282 16-Core Processor
> 
> However, libvirt is detecting this as EPYC-IBPB without the ssbd flags?
> 
>   
> x86_64
> EPYC-IBPB
> AMD
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>   

in 4.3 we still use flags instead of libvirt feature detection (which we’re 
fixing in 4.4, but so far it’s playing to your advantage:) 
So seeing “ssbd" below in cpuinfo should be enough to detect the oVirt type 
with SSBD. Where exatly you see that not working?
 
Thanks,
michal

> 
> 
> [root@node01 ~]# grep ssbd /var/cache/libvirt/qemu/capabilities/*.xml
>   
>   
>   
>   
> 
> But the flag is there:
> 
> [root@node01 ~]# grep ssbd /proc/cpuinfo | tail -n1
> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
> mca cmov
> pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
> pdpe1gb rdtscp lm constant_tsc art rep_good nopl xtopology nonstop_tsc
> extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16
> sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy
> svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs
> skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb
> cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall
> fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb
> sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total
> cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save
> tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
> avic v_vmsave_vmload vgif umip overflow_recov succor smca
> 
> I tried adding "options kvm_amd avic=1" as well as "options kvm_amd
> avic=0" to /etc/modprobe.d/kvm.conf (always with reboots), adding
> mitigations=off to grub.. I can't think of any other solution.
> 
> I just can't get the oVirt engine running with the ssbd flag. Seems cpu
> can do this, oVirt can do this, libvirt does not detect the cpu
> correctly or at least ignores it. But the hosted engine demands it.
> 
> I am at a loss. Any help is oh-so-greatly appreciated.
> 
> -Chris.
> 
> --
>Christian Reiss - em...@christian-reiss.de /"\  ASCII Ribbon
>  supp.

[ovirt-users] Re: Wrong CPU?

2019-11-18 Thread Christian Reiss

Ugh,

first off thanks for all your effort and information. Much obliged.
But this also means that I am looking at a lng time before I can go
to production with this cluster. Now I am sad.

Would it be an option to run the engine on dedicated hardware and
control the cluster from there? Or is that thing in total not usable?

-Chris.

On 18/11/2019 07:25, Juhani Rautiainen wrote:

Hi!

Had to get back to work to check which CPU we had. We have AMD Epyc
7281 and ovirt CPU Type is AMD EPYC IBPB SSBD. It seems that your CPU
is the next generation (Zen2) and I'm pretty sure that problem is with
Qemu version. As far as I can see from git there is not even Zen2
support in latest Qemu (checking by target/i386/cpu.c)? I mean they
added Hygon Dhyana (never even heard about this chinese AMD EPYC
clone) and in that discussion there was reference to Zen2
architecture. So biggest problem for oVirt seems to come from
upstream. I mean that Zen2 is quite good for virtualization and it's
going to sell a lot. Maybe AMD should help with that push?

-Juhani

On Fri, Nov 15, 2019 at 9:03 PM Christian Reiss
wrote:

Sorry,

I meant EPYC, not Ryzen.
How did you solve your EPYC issue?

-Chris.

On 15/11/2019 18:55, Juhani Rautiainen wrote:

Hi!

It might be that the Qemu in oVirt doesn't recognize the Ryzen. That
was case with Epyc when I started using oVirt. It was reconized as a
Opteron G2 which caused lot's of problems when upgrading to 4.3.

-Juhani

On Fri, Nov 15, 2019 at 6:45 PM Christian Reiss
wrote:

Hey folks,

running an AMD Ryzen CPU here:

processor : 0
vendor_id : AuthenticAMD
cpu family : 23
model : 49
model name : AMD EPYC 7282 16-Core Processor

However, libvirt is detecting this as EPYC-IBPB without the ssbd flags?

x86_64
EPYC-IBPB
AMD

[root@node01 ~]# grep ssbd /var/cache/libvirt/qemu/capabilities/*.xml

But the flag is there:

[root@node01 ~]# grep ssbd /proc/cpuinfo | tail -n1
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
pdpe1gb rdtscp lm constant_tsc art rep_good nopl xtopology nonstop_tsc
extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16
sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy
svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs
skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb
cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall
fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb
sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total
cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
avic v_vmsave_vmload vgif umip overflow_recov succor smca

I tried adding "options kvm_amd avic=1" as well as "options kvm_amd
avic=0" to /etc/modprobe.d/kvm.conf (always with reboots), adding
mitigations=off to grub.. I can't think of any other solution.

I just can't get the oVirt engine running with the ssbd flag. Seems cpu
can do this, oVirt can do this, libvirt does not detect the cpu
correctly or at least ignores it. But the hosted engine demands it.

I am at a loss. Any help is oh-so-greatly appreciated.

-Chris.

--
Christian Reiss - em...@christian-reiss.de /"\ ASCII Ribbon
supp...@alpha-labs.net \ /Campaign
X against HTML
WEB alpha-labs.net / \ in eMails

GPG Retrieval https://gpg.christian-reiss.de
GPG ID ABCD43C5, 0x44E29126ABCD43C5
GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5

--
Christian Reiss - em...@christian-reiss.de /"\ ASCII Ribbon
supp...@alpha-labs.net \ /Campaign
X against HTML
WEB alpha-labs.net / \ in eMails

GPG Retrieval https://gpg.christian-reiss.de
GPG ID ABCD43C5,

[ovirt-users] Re: Wrong CPU?

2019-11-16 Thread Juhani Rautiainen

Hi!

It might be that the Qemu in oVirt doesn't recognize the Ryzen. That
was case with Epyc when I started using oVirt. It was reconized as a
Opteron G2 which caused lot's of problems when upgrading to 4.3.

-Juhani

On Fri, Nov 15, 2019 at 6:45 PM Christian Reiss
 wrote:
>
> Hey folks,
>
> running an AMD Ryzen CPU here:
>
> processor   : 0
> vendor_id   : AuthenticAMD
> cpu family  : 23
> model   : 49
> model name  : AMD EPYC 7282 16-Core Processor
>
> However, libvirt is detecting this as EPYC-IBPB without the ssbd flags?
>
>  
>x86_64
>EPYC-IBPB
>AMD
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>  
>
>
> [root@node01 ~]# grep ssbd /var/cache/libvirt/qemu/capabilities/*.xml
>  
>  
>  
>  
>
> But the flag is there:
>
> [root@node01 ~]# grep ssbd /proc/cpuinfo | tail -n1
> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
> cmov
> pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
> pdpe1gb rdtscp lm constant_tsc art rep_good nopl xtopology nonstop_tsc
> extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16
> sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy
> svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs
> skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb
> cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall
> fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb
> sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total
> cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save
> tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
> avic v_vmsave_vmload vgif umip overflow_recov succor smca
>
> I tried adding "options kvm_amd avic=1" as well as "options kvm_amd
> avic=0" to /etc/modprobe.d/kvm.conf (always with reboots), adding
> mitigations=off to grub.. I can't think of any other solution.
>
> I just can't get the oVirt engine running with the ssbd flag. Seems cpu
> can do this, oVirt can do this, libvirt does not detect the cpu
> correctly or at least ignores it. But the hosted engine demands it.
>
> I am at a loss. Any help is oh-so-greatly appreciated.
>
> -Chris.
>
> --
>   Christian Reiss - em...@christian-reiss.de /"\  ASCII Ribbon
> supp...@alpha-labs.net   \ /Campaign
>   X   against HTML
>   WEB alpha-labs.net / \   in eMails
>
>   GPG Retrieval https://gpg.christian-reiss.de
>   GPG ID ABCD43C5, 0x44E29126ABCD43C5
>   GPG fingerprint = 9549 F537 2596 86BA 733C  A4ED 44E2 9126 ABCD 43C5
>
>   "It's better to reign in hell than to serve in heaven.",
>John Milton, Paradise lost.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/PPXT55FJZESYOAOPR7HY5LOHTYELWDN6/



-- 
Juhani Rautiainen   jra...@iki.fi
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WD6XANLPRISIQ5GQ77HMP4THR36NFITB/

[ovirt-users] Re: Wrong CPU?

2019-11-15 Thread Christian Reiss


Sorry,

I meant EPYC, not Ryzen.
How did you solve your EPYC issue?

-Chris.

On 15/11/2019 18:55, Juhani Rautiainen wrote:

Hi!

It might be that the Qemu in oVirt doesn't recognize the Ryzen. That
was case with Epyc when I started using oVirt. It was reconized as a
Opteron G2 which caused lot's of problems when upgrading to 4.3.

-Juhani

On Fri, Nov 15, 2019 at 6:45 PM Christian Reiss
 wrote:


Hey folks,

running an AMD Ryzen CPU here:

processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 23
model   : 49
model name  : AMD EPYC 7282 16-Core Processor

However, libvirt is detecting this as EPYC-IBPB without the ssbd flags?

  
x86_64
EPYC-IBPB
AMD

























  


[root@node01 ~]# grep ssbd /var/cache/libvirt/qemu/capabilities/*.xml
  
  
  
  

But the flag is there:

[root@node01 ~]# grep ssbd /proc/cpuinfo | tail -n1
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
pdpe1gb rdtscp lm constant_tsc art rep_good nopl xtopology nonstop_tsc
extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16
sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy
svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs
skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb
cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall
fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb
sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total
cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
avic v_vmsave_vmload vgif umip overflow_recov succor smca

I tried adding "options kvm_amd avic=1" as well as "options kvm_amd
avic=0" to /etc/modprobe.d/kvm.conf (always with reboots), adding
mitigations=off to grub.. I can't think of any other solution.

I just can't get the oVirt engine running with the ssbd flag. Seems cpu
can do this, oVirt can do this, libvirt does not detect the cpu
correctly or at least ignores it. But the hosted engine demands it.

I am at a loss. Any help is oh-so-greatly appreciated.

-Chris.

--
   Christian Reiss - em...@christian-reiss.de /"\  ASCII Ribbon
 supp...@alpha-labs.net   \ /Campaign
   X   against HTML
   WEB alpha-labs.net / \   in eMails

   GPG Retrieval https://gpg.christian-reiss.de
   GPG ID ABCD43C5, 0x44E29126ABCD43C5
   GPG fingerprint = 9549 F537 2596 86BA 733C  A4ED 44E2 9126 ABCD 43C5

   "It's better to reign in hell than to serve in heaven.",
John Milton, Paradise lost.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PPXT55FJZESYOAOPR7HY5LOHTYELWDN6/






--
 Christian Reiss - em...@christian-reiss.de /"\  ASCII Ribbon
   supp...@alpha-labs.net   \ /Campaign
 X   against HTML
 WEB alpha-labs.net / \   in eMails

 GPG Retrieval https://gpg.christian-reiss.de
 GPG ID ABCD43C5, 0x44E29126ABCD43C5
 GPG fingerprint = 9549 F537 2596 86BA 733C  A4ED 44E2 9126 ABCD 43C5

 "It's better to reign in hell than to serve in heaven.",
  John Milton, Paradise lost.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5WLHQXMLLKAXIPLLYWIMI2DXSUWJM4DZ/

[ovirt-users] Re: Wrong CPU performance report

2019-02-03 Thread Liran Rotenberg

Hi,
If your windows guest is with update 1803 or above you might hit this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1644693

Regards,
Liran.

On Sun, Feb 3, 2019 at 11:28 PM Hetz Ben Hamo  wrote:

> Hi,
>
> I'm running oVirt 4.2.7.1. I installed Windows 10 pro as a guest, along
> with QXL and all the drivers, as well as QEMU guest agent.
>
> While Windows reports a CPU usage of something like 2-4% when idle, oVirt
> reports 24-27% CPU usage.
>
> Bug? should I report it?
>
> Thanks
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/OJMAVROXJOSJ2B33BZ5XFJ2QGHONM65Z/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MK5QWLJTGPQPLMSFLYR52UQXSVZU5BBR/

[ovirt-users] Re: Wrong CPU type recognized on a new Pentium G4560 Kaby Lake

[ovirt-users] Re: Wrong CPU?

[ovirt-users] Re: Wrong CPU?

[ovirt-users] Re: Wrong CPU?

[ovirt-users] Re: Wrong CPU?

[ovirt-users] Re: Wrong CPU?

[ovirt-users] Re: Wrong CPU?

[ovirt-users] Re: Wrong CPU performance report

8 matches

Site Navigation

Mail list logo

Footer information