Ryzen, Threadripper, EPYC - all have the same virtualization down to the
last bit (the last option that you mentioned).



On Fri, Feb 8, 2019 at 9:26 PM Edward Berger <[email protected]> wrote:

> I'm wondering what cluster cpu compatibility version the Ryzen 2700 would
> go under?
> It used to default to Opteron G3 when I tried it before, which is now
> "unsupported" as of ovirt 4.3.
> CentOS 7 complains about "untested" CPU with Ryzen 2700 in my experience.
> Maybe Fedora is better there.
>
> Here are what shows up in the available cluster options... I'm not sure
> where and how its defined for specific CPUs.
>
>
>    - AMD Opteron G4
>    - AMD Opteron G5
>    - AMD EPYC
>    - AMD EPYC IBPB SSBD
>
>
>
> On Fri, Feb 8, 2019 at 2:07 PM Hetz Ben Hamo <[email protected]> wrote:
>
>> Yup, and nested is enabled.
>>
>> The HE is booting and starting to run, I get the status messages about
>> starting etc, so it's not related to CPU functionality IMHO.
>>
>>
>> On Fri, Feb 8, 2019 at 9:02 PM Greg Sheremeta <[email protected]>
>> wrote:
>>
>>> Does amd require a nested flag set like Intel does?
>>>
>>> On Fri, Feb 8, 2019, 12:03 PM Hetz Ben Hamo <[email protected]> wrote:
>>>
>>>> Yes, that's the first thing I did and I checked in the VM that the kvm
>>>> and kvm_amd module loaded.
>>>>
>>>>
>>>> On Fri, Feb 8, 2019 at 6:42 PM femi adegoke <[email protected]>
>>>> wrote:
>>>>
>>>>> Do you have your CPU type set for "host-passthrough"?
>>>>>
>>>>> On Feb 8 2019, at 8:25 am, Hetz Ben Hamo <[email protected]> wrote:
>>>>>
>>>>> I'm to setup an oVirt enviroment using virt-manager on Fedora 29 to
>>>>> record some videos. For that - I'm using nested virtualization.
>>>>>
>>>>> The problem - after it's setting the HE - it goes up and down like
>>>>> crazy (I defined the email setting to get all the messages) until it gives
>>>>> up.
>>>>>
>>>>> enclosed - a gzipped vdsm.log.
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list -- [email protected]
>>>>> To unsubscribe send an email to [email protected]
>>>>> 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/[email protected]/message/L45YCPOPV7DEC4KG7NEHTYRPJKN5EDOK/
>>>>>
>>>>> _______________________________________________
>>>> Users mailing list -- [email protected]
>>>> To unsubscribe send an email to [email protected]
>>>> 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/[email protected]/message/XSNLP34EKMTB4NASFKMZXMXRZU4HFVXB/
>>>>
>>> _______________________________________________
>> Users mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>> 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/[email protected]/message/7H5VAMLDQRAJXSCLGBLTJKOZ62Y5NXVZ/
>>
>
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/BC6AYUNUOQIFIAMI2B7LNK5Q37QL3XD5/

Reply via email to