On Mon, Sep 26, 2016 at 11:10 AM, Gianluca Cecchi <[email protected] > wrote:
> > >> >>> 25.09.2016, 09:14, "Roy Golan" <[email protected]>: >>> >>> You need to edit the vm in the webui and increase the memory there. The >>> next cold boot of the machine will load it with the new config. Do note >>> that the engine has an interval which triggers the creation of the new >>> vm.conf. The interval config item can be checked using >>> >>> ``` >>> >>> >> >> > Hello, from which version? > > In my case I have "oVirt Engine Version: 4.0.2.7-1.el7.centos" and I get > this error if I try to modify from web admin, but I don't understand if it > could be related with something different.... > > https://drive.google.com/file/d/0BwoPbcrMv8mvdHRHamZJZm5iRkU/ > view?usp=sharing > > Currently general pane for hosted engine vm is this one, so that OS > appears as "Other OS" (the engien vm was installed from appliance > initially): > https://drive.google.com/file/d/0BwoPbcrMv8mvbkkyejJ4V1gxd2M/ > view?usp=sharing > > Hi Gianluca, are you able to recall or verify which version of ovirt-hosted-engine-setup did you used when you initially created your hosted-engine env? I suspect that your issue could be somehow related to https://bugzilla.redhat.com/show_bug.cgi?id=1328921 and https://bugzilla.redhat.com/show_bug.cgi?id=1339306 which have been fixed which patch http://gerrit.ovirt.org/57906 for new deployment but not for who deployed before that and than simply upgraded engine rpms over his working engine VM. For 4.1 we are thinking at a mechanism to upgrade also engine VM definition when running engine-setup, currently it's not available. Probably the best option to fix it right now is something like: - set global maintenance mode - manually removing the engine VM from the engine DB (to let the auto-import procedure trigger again) - shutdown the engine VM - copy your /var/run/ovirt-hosted-engine-ha/vm.conf somewhere - edit it adding the required devices - start the engine VM with hosted-engine --vm-start --vm-conf=myvm.conf - wait for the auto-import procedure to kick in and re-import the engine VM with the additional devices - exit global maintenance mode Roy, do you see something simpler to achieve the same result? > Thanks, > Gianluca > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
