Resuming stopped VMs from OpenNebula 4 in OpenNebula 5
Problem: VMs that were started in OpenNebula 4 and STOPPED, get stuck in state PENDING when resuming.
The underlying problem seems to be that the VNC port range used by OpenNebula has changed between v4 and v5 and that OpenNebula 5 refuses to schedule an VM with a ‘old’ VNC port.
- You can change the configuration of a PENDING VM. You can go to the Conf tab and click the green Update Configuration button.
- Go to the Input/Output subtab and change the Graphics radio button from VNC to none.
- After clicking Update the VM should be rescheduled and change to state PROLOG in a few seconds/minutes.