Post

5 followers Follow
0
Avatar

Importing VM threw error - HOLD Status

I was having serious problems connecting imported wild vms through VNC, so in order to run some tests, I cloned a productive VM, unfortunately during the import process to vOneCloud, sunstone threw an error and presented the VM with HOLD Status, currently I cannot access, recover or even delete the VM. I wonder which is the procedure to remove this VM with HOLD Status? I've checked that the cloned VM is also listed at the ZOMBIE section. Thanks

Juan M.

Please sign in to leave a comment.

6 comments

1
Avatar

hi, this is a known problem.

When OpenNebula import any wild a reconfigure operation takes place, this operation writes in the vmx configuration certain aspects like the vnc port.

The problem comes when you use a machine "touched" by opennebula. for example if you try to clone the machine (vCenter side) you will be cloning openNebula configuration too, then  if you try to import your cloned machine in OpenNebula you could experience a lot of problems due to the old openNebula config.

To avoid this situation before the import operation you can browse in the proper vmx of the machine and delete the config:

remotedisplay.vnc.enabled  = "TRUE"
remotedisplay.vnc.port         = "X"
remotedisplay.vnc.ip            = "0.0.0.0"

You should delete too any opennebula reference but these are the 3 attributes that are causing the HOLD behaviour.

 

Regards 

 

Sergio Semedi Barranco 1 vote
Comment actions Permalink
0
Avatar

hi. i have the same problem. i see the solution down here. but if i disable those aspects of the vmx file, how will i able to do a console connection to the vm?

Lior Meshi 0 votes
Comment actions Permalink
0
Avatar

When importing a VM, if no VNC details are defined in the .vmx file, OpenNebula will choose an VNC port and reconfigure the VM, so you can still access it through VNC. 

vOneCloud Support Team 0 votes
Comment actions Permalink
0
Avatar

oh. cool. but wouldn't it conflict at some point? there are so many ports in the vnc port range, no?

Lior Meshi 0 votes
Comment actions Permalink
0
Avatar

vOneCloud reuses VNC ports from terminated VMs. This only is a problem if you have a huge number of VMs per vCenter cluster.

vOneCloud Support Team 0 votes
Comment actions Permalink