[one-users] How to fix status manually from SUSPENDED to RUNNING

[Carlos Martín Sánchez]

Hi,

On Tue, Jan 6, 2015 at 7:25 AM, Steve @ MyEvolve <steve at myevolve.com> wrote:

> Hello List,
>
> I did something stupid.
>
> I moved data centers and then after exhaustion and not thinking clearly...
>
> I dumped the database and did a find/replace to change the IP space after
> I had manually ssh into each vm and changed.
>
> The problem is that the version of the DB I reimported had each vm in
> suspended mode.
>
> Each VM is running correctly.  How do I update the db/one to know this
> without disrupting the running vms?
>
> Thanks in advance for any help!
>
> Steve
>

The VM state cannot be changed easily. I think the safest way to fix your
problem would be to edit the driver to exit 0, and then "false-resume" your
VMs. This can be done with the following steps:

- In the front-end, edit the /var/lib/one/remotes/vmm/<hypervisor>/restore
file.
- To send the update file to each host, execute ''onehost sync --force".
- Then you can run "onevm resume" on the suspended VMs, and they should
move to the running state.
- After that, restore the original driver script and use the onehost sync
command again.

Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org <http://www.opennebula.org/> | cmartin at opennebula.org |
@OpenNebula <http://twitter.com/opennebula> <cmartin at opennebula.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20150108/c50f048b/attachment-0001.htm>