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 - email@christian-reiss.de /"\ ASCII Ribbon support@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.