> On Jan 22, 2021, at 10:11, Arik Hadas wrote:
>
> On Thu, Jan 21, 2021 at 9:27 PM Joseph Gelinas wrote:
> I found `engine-setup
> --otopi-environment=OVESETUP_CONFIG/continueSetupOnHEVM=bool:True` from [1]
> and now have the ovirt-engine web interface reachable again. But do have one
> more
On Thu, Jan 21, 2021 at 9:27 PM Joseph Gelinas wrote:
> I found `engine-setup
> --otopi-environment=OVESETUP_CONFIG/continueSetupOnHEVM=bool:True` from [1]
> and now have the ovirt-engine web interface reachable again. But do have
> one more question; when I try to change the Custom Chipset/Firmw
I found `engine-setup
--otopi-environment=OVESETUP_CONFIG/continueSetupOnHEVM=bool:True` from [1] and
now have the ovirt-engine web interface reachable again. But do have one more
question; when I try to change the Custom Chipset/Firmware Type to Q35 Chipset
with BIOS, I get the error; HostedEn
Removing those two lines got the hosted engine vm booting again, so that is a
great help. Thank you.
Now I just need the web interface of ovirt-engine to work again. I feel like I
might have run things out of order and forgot to do `engine-setup` as part of
the update of hosted engine. Though w
On Thu, Jan 21, 2021 at 8:57 AM Joseph Gelinas wrote:
> Hi,
>
> I recently did some updates of ovirt from 4.4.1 or 4.4.3 to 4.4.4, also
> setting the default datacenter from 4.4 to 4.5 and making the default bios
> q35+eufi. Unfortunately quite a few things. Now however hosted engine
> doesn't bo
5 matches
Mail list logo