Dear Andrej and Martin:
I just wanted to follow-up and thank you both so very much. I was able to
update to the latest 4.1.9 and that resolved my issues - engine started just
fine, all vm's are up. My apologies for the delayed update, I had back surgery
and was out a while.
Again, I really a
Hi all,
we decided to issue an updated package to the oVirt 4.1 repository
that should fix this for all users. We still consider 4.1 an EOL
release, but we think this upgrade path should be fixed anyway.
Metadata are refreshing as we speak. You can also download the package
manually from the repo
Thank you again so very much Andrej! I am going to try this right now...
Respectfully,
Charles
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
The local vm.conf is overriden by the configuration on the shared storage,
but the bug with VM having 4 MB of RAM instead of 4 GB is already fixed:
https://bugzilla.redhat.com/1524331
Try upgrading the ovirt-hosted-engine-ha and ovirt-hosted-engine-setup
packages on the ovirt-node.
Specifically, t
OK, I think the inability to change /var/run/ovirt-hosted-engine-ha/vm.conf
might have something to do with HE configuration having been moved to shared
storage?
(https://ovirt.org/develop/release-management/features/sla/hosted-engine-configuration-on-shared-storage/)
I am using NFS shares on a
I cannot get /var/run/ovirt-hosted-engine-ha/vm.conf to keep my edit of
"memSize=4" to "memSize=4096" --> it keeps reverting. I have confirmed that HE
is down --> suggestions?
Thanks,
Charles
___
Users mailing list -- users@ovirt.org
To unsubscribe se
Andrej, thank you so much!!!
I knew I was having issues with X11, and was trying to troubleshoot that here.
Your suggestion to setup port forwarding, with some tweaks, worked!!! Thank
you thank you.
I am now able to see that HostedEngine is not booting, it states "cannot
allocate kernel buff
This is an error from the VNC client, probably related to X forwarding.
Try setting the DISPLAY environment variable before running remote-viewer:
'export DISPLAY=0:0'
Or alternatively, you could setup port forwarding when connecting the the
host,
and then run the VNC client on your local machine:
> Hi,
>
> You could try accessing the engine VM using the VNC.
> First, set the VNC password using 'hosted-engine --add-console-password',
> and then connect to the host using a VNC viewer, for example:
> 'remove-viewer vnc://HOST_IP:5900'
>
> The liveliness check just checks if the web UI is run
Hi,
You could try accessing the engine VM using the VNC.
First, set the VNC password using 'hosted-engine --add-console-password',
and then connect to the host using a VNC viewer, for example:
'remove-viewer vnc://HOST_IP:5900'
The liveliness check just checks if the web UI is running and reachab
Hi,
I am still working to resolve my issue - is there any further detail or
clarification I can provide that might help? I really appreciate your time.
Thank you,
Charles
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-
11 matches
Mail list logo
