[ovirt-users] Re: HCL: 4.3.7: Hosted engine fails

2020-01-08 Thread Christian Reiss
Oh, shoot. Replied to the wrong email. I meant to reply to my own with subject "[ovirt-users] HostedEngine Deployment fails on AMD EPYC 7402P 4.3.7" How it came to reply to *this* thread I am unsure. My apologies. -Chris. On 08/01/2020 10:39, Christian Reiss wrote: Hey, for the record

[ovirt-users] Re: HCL: 4.3.7: Hosted engine fails

2020-01-08 Thread Christian Reiss
Hey, for the record and if someone else is looking for a solution: The given ones were not solving the issue, even editing the config via virsh semi-failed as the ansible playbook kept deleting the vm and re-creating it, always resulting in new UUIDs. What did solve the issue was to use an

[ovirt-users] Re: HCL: 4.3.7: Hosted engine fails

2019-12-12 Thread thomas
You may just be able to use the username and password already created during the installation: vdsm@ovirt/shibboleth. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:

[ovirt-users] Re: HCL: 4.3.7: Hosted engine fails

2019-12-12 Thread Ralf Schenk
Hello, hosted engine deployment simply fails on EPYC with 4.3.7. See my earlier posts "HostedEngine Deployment fails on AMD EPYC 7402P 4.3.7". I was able to get this up and running by modifying HostedEngine VM XML while Installation tries to start the engine. Great fun ! virsh -r dumpxml

[ovirt-users] Re: HCL: 4.3.7: Hosted engine fails

2019-12-11 Thread Robert Webb
I could not find if that CPU supported SSBD or not. Log into one your nodes via console and run, "cat /proc/cpuinfo" and check the "flags" section and see if SSBD is listed. If not, then look at your cluster config under the "General" section and see what it has for "Cluster CPU Type". Make