Re: [libvirt-users] Usable and non-usable CPU models in nested virtualization

2018-12-12 Thread Milan Zamazal
Thank you for explanation, it's clear to me now. One last question: Is there a way to get supported compatibility modes on POWER? For instance, I get the following from domcapabilities on a POWER9 machine: POWER9 IBM How can I find out that POWER8 guests ar

Re: [libvirt-users] Usable and non-usable CPU models in nested virtualization

2018-12-11 Thread Jiri Denemark
On Tue, Dec 11, 2018 at 10:45:12 +0100, Milan Zamazal wrote: > Jiri Denemark writes: > > > On Fri, Dec 07, 2018 at 11:52:38 +0100, Milan Zamazal wrote: > >> Hi, some custom CPU models are reported from > >> virConnectGetDomainCapabilities as usable='yes' on a physical machine > > > >> while as us

Re: [libvirt-users] Usable and non-usable CPU models in nested virtualization

2018-12-11 Thread Milan Zamazal
Jiri Denemark writes: > On Fri, Dec 07, 2018 at 11:52:38 +0100, Milan Zamazal wrote: >> Hi, some custom CPU models are reported from >> virConnectGetDomainCapabilities as usable='yes' on a physical machine > >> while as usable='no' inside a VM running on the same machine. That's >> not completel

Re: [libvirt-users] Usable and non-usable CPU models in nested virtualization

2018-12-11 Thread Jiri Denemark
On Fri, Dec 07, 2018 at 11:52:38 +0100, Milan Zamazal wrote: > Hi, some custom CPU models are reported from > virConnectGetDomainCapabilities as usable='yes' on a physical machine > while as usable='no' inside a VM running on the same machine. That's > not completely surprising. > > But what surp