Migrating a VM in 'POWEROFF' state

Community Support
1

Hi everyone,

I’m trying to simulate a node replacement scenario within OpenNebula. As part of my simulation I require a VM to be migrated to another node. The problem I’m facing is when a VM is in ‘POWEROFF’ state, are these not able to migrated in this state?

Sorry if this has been answered already.

Kind Regards,
Joshua Blake

2

The migrate action is available for VMs in poweroff.
Is it not working for you? Do you get any error messages?

3

Hi Carlos,

Thank you for responding. Here is what I get when I try to migrate a VM.

[admin@node0 ~]$ onevm list
ID USER GROUP NAME STAT UCPU UMEM HOST TIME
1 administ oneadmin nw-ubuntu poff 0 0K 192.168.0.152 77d 22h20
2 customer customer nw-ubuntu-customer-group-2 poff 0 0K 192.168.0.151 76d 23h39
3 customer customer nw-ubuntu-customer-group-3 poff 0 0K 192.168.0.152 76d 23h37
36 administ oneadmin windows7-test-vd poff 0 0K 192.168.0.152 2d 23h48
37 administ oneadmin windows7-test-sd poff 0 0K 192.168.0.151 2d 23h48
[admin@node0 ~]$ onevm migrate 36 192.168.0.151
[VirtualMachineMigrate] Wrong state to perform action

Kind Regards,
Joshua Blake

4

What OpenNebula version are you using?

5

How do I check that? Sorry.

6

oned -v, or log files

7

[admin@node0 ~]$ oned -v
Copyright 2002-2014, OpenNebula Project (OpenNebula.org), C12G Labs

OpenNebula 4.8.0 is distributed and licensed for use under the terms of the
Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0).

8

There’s the problem, the migration from poweroff was added later. The last stable release is 4.14.2, the upgrade documentation is:
http://docs.opennebula.org/4.14/release_notes/release_notes/upgrade_48.html