I think you are supposed to change such parameters from the engine ui, not
>> >
>> > the modified file would be such that:
>> >
>> > [root@ovirt02 images]# diff /var/run/ovirt-hosted-engine-ha/vm.conf
>> > /root/alternate_vm.conf
>> > 1,2c1,2
>> > < cpuType=Broadwell
>> > < emulatedMachine=pc-i440fx-rhel7.3.0
>> > ---
>> >> cpuType=qemu64
>> >> emulatedMachine=pc-i440fx-rhel7.2.0
>> > [root@ovirt02 images]#
>>
>> No idea about your specific issue or whether this can fix it, but you can
>> try.
>> Especially if you can test on a test env...
>>
>> Best,
>> --
>> Didi
>
>
> And in fact the engine vm is now up again with the customized parameters
> How can I have it permanent? Frome where on shared storage are they read?
by directly manipulating the shared storage using [1]. But I didn't try this
myself, not sure if cpu type can be changed.
[1] http://www.ovirt.org/develop/release-management/features/ sla/hosted-engine-edit- configuration-on-shared- storage/
>
> Possibly the problems is generated by my nested environment:
>
> L0 = ESXi 6.0 U2 on NUC6i5syh
> L1 are my oVirt hosts on this L0
> L2 is my engine VM that doesn't start in 4.1.3
>
> it seems that
> cpuType=Broadwell and/or emulatedMachine=pc-i440fx-rhel7.3.0 No idea about this, adding Michal.
> generates problems....
Best,
--
>
> And I think I would have same problems with ordinary VMs, correct?
> Gianluca
Didi