It looks like VNC works if I manually vMotion the VM to the host that vOneCloud believes it is running on. Can vOneCloud periodically update the host a VM is running on?
Change frequency of VM host update
We're struggling to get VNC to work properly as vCenter is moving VMs around in the background with vMotion, and vOneCloud isn't updating VM hosts fast enough to cope. This results in it thinking a VM is on a different host to the one it is actually running on, and VNC is getting "connection refused" errors in novnc.log.
Is there a way I can customise this to update more frequently?
Please sign in to leave a comment.
You are probably being hit by this: https://github.com/OpenNebula/one/issues/2477
It will be solved in future versions of vOneCloud.
Thanks for sharing this. Do you know when this will be implemented?