Hi Karsten,
I don't know how to reproduce your problem... Does this happen with any
other VM? Did you try to restart opennebula?
Please open a bug at http://dev.opennebula.org and include the VM xml
output, the individual VM log file, and the RequestManager log lines from
oned.log.
Regards
--
Ca
Hi,
output from onevm show -x
3
3
output from onevm list -x
1418670269
3
3
So it seems that the value 3 is present both places.
- Karsten
On 15/12/14 11:03, Carlos Martín Sánchez wrote:
Hi,
That is strange. Let's check the consistency in the DB. Can you
confirm the state fr
Hi,
That is strange. Let's check the consistency in the DB. Can you confirm the
state from the xml output in onevm show -x *and* onevm list -x? The fields
STATE and LCM_STATE should be both "3" for VM 130.
Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made
Hi,
When I try to live migrate or migrate one of my VM's i get this.
onevm migrate --live 130 2
[VirtualMachineMigrate] Wrong state to perform action
The state of the VM is
STATE : ACTIVE
LCM_STATE : RUNNING
I am a little confused.
- Karsten
___
It is on one version 4.8
- Karsten
On 13/12/14 21:44, Karsten Nielsen wrote:
Hi,
When I try to live migrate or migrate one of my VM's i get this.
onevm migrate --live 130 2
[VirtualMachineMigrate] Wrong state to perform action
The state of the VM is
STATE : ACTIVE
LCM_STATE
Hi,
Thanks Carlos, that did the trick.
Yours,
Steffen
Just for the records:
update history
set body =
'5node-b...3'
where vid=1006 and seq=5;
and of course with the correct values for vid and seq
determined before, and the body XML with REASON edited.
On Tue, 2012-09-25 at 18:47 +0200
Hi Steffen,
Looks like you are right, a migration failed and somehow left the history
records corrupted.
If you only need to be able to migrate, change the reason of history 7 to
'3'. To do so, stop opennebula, do a DB backup, and update
the body column of the history table. As I said, do this fo
Hi,
sorry for replying to self. I found a thread from august this year,
http://comments.gmane.org/gmane.comp.distributed.opennebula.user/7554
which I missed in my earlier searches, where Shantanu Pavgi suggests
to clean the history and vm_pool tables.
To avoid messing this up, which entries in h
Hi,
I have a working one-3.0 cluster, and for upgrading to 3.6
I need to move around VMs. The cluster has been up and
running for about a year now.
At least two VMs on one host are stubbornly refusing
to live-migrate:
oneadmin@cumulus:~$ onevm livemigrate 1004 55
[VirtualMachineDeploy] Wrong
