I have 2 VMs in 'UNKNOWN' state after migration. They are running
fine and can be accessed through the VNC. Also, other VMs on same host
are in ‘RUNNING’ state. Any ides what is happening here and how it can
be rectified?
I'm afraid that at present we are a little behind in running 4.6.2-1
(we are planning to catch up soon). The hosts are fine in state ‘ON’. It
looks like the VM state is toggeling between ‘RUNNING’ and ‘UNKNOWN’
(see below).
Rgeards,
Gerry
Typical entry for onmed.log
Tue Mar 24 16:40:07 2015 [VMM][D]: VM 3176 successfully monitored: STATE=a USEDCPU=0.5 USEDMEMORY=2097152 NETRX=20531340 NETTX=9450496
Mon Mar 23 12:00:57 2015 [DiM][I]: New VM state is ACTIVE.
Mon Mar 23 12:00:57 2015 [LCM][I]: New VM state is PROLOG.
Mon Mar 23 12:00:57 2015 [VM][I]: Virtual Machine has no context
Mon Mar 23 12:01:43 2015 [LCM][I]: New VM state is BOOT
Below are formatted log entries missing from previous reply
Typical entry for onmed.log
Tue Mar 24 16:40:07 2015 [VMM][D]: VM 3176 successfully monitored: STATE=a USEDCPU=0.5 USEDMEMORY=2097152 NETRX=20531340 NETTX=9450496
Mon Mar 23 12:00:57 2015 [DiM][I]: New VM state is ACTIVE.
Mon Mar 23 12:00:57 2015 [LCM][I]: New VM state is PROLOG.
Mon Mar 23 12:00:57 2015 [VM][I]: Virtual Machine has no context
Mon Mar 23 12:01:43 2015 [LCM][I]: New VM state is BOOT
Mon Mar 23 12:01:43 2015 [VMM][I]: Generating deployment file:
/var/lib/one/vms/3176/deployment.0
Mon Mar 23 12:01:43 2015 [VMM][I]: ExitCode: 0
Mon Mar 23 12:01:43 2015 [VMM][I]: Successfully execute network driver
operation: pre.
Mon Mar 23 12:01:45 2015 [VMM][I]: ExitCode: 0
Mon Mar 23 12:01:45 2015 [VMM][I]: Successfully execute virtualization
driver operation: deploy.
Mon Mar 23 12:01:45 2015 [VMM][I]: ExitCode: 0
Mon Mar 23 12:01:45 2015 [VMM][I]: Successfully execute network driver
operation: post.
Mon Mar 23 12:01:46 2015 [LCM][I]: New VM state is RUNNING
Mon Mar 23 14:11:36 2015 [LCM][I]: New VM state is MIGRATE
Mon Mar 23 14:11:36 2015 [VMM][I]: Successfully execute transfer manager
driver operation: tm_premigrate.
Mon Mar 23 14:11:36 2015 [VMM][I]: ExitCode: 0
Mon Mar 23 14:11:36 2015 [VMM][I]: Successfully execute network driver
operation: pre.
Mon Mar 23 14:11:44 2015 [VMM][I]: ExitCode: 0
Mon Mar 23 14:11:44 2015 [VMM][I]: Successfully execute virtualization
driver operation: migrate.
Mon Mar 23 14:11:44 2015 [VMM][I]: ExitCode: 0
Mon Mar 23 14:11:44 2015 [VMM][I]: Successfully execute network driver
operation: clean.
Mon Mar 23 14:11:44 2015 [VMM][I]: ExitCode: 0
Mon Mar 23 14:11:44 2015 [VMM][I]: Successfully execute network driver
operation: post.
Mon Mar 23 14:11:44 2015 [VMM][I]: Successfully execute transfer manager
driver operation: tm_postmigrate.
Mon Mar 23 14:11:45 2015 [LCM][I]: New VM state is RUNNING
Mon Mar 23 14:12:10 2015 [LCM][I]: New VM state is UNKNOWN
Mon Mar 23 14:21:46 2015 [VMM][I]: VM found again, state is RUNNING
Mon Mar 23 14:22:39 2015 [LCM][I]: New VM state is UNKNOWN
Mon Mar 23 14:32:47 2015 [VMM][I]: VM found again, state is RUNNING
Mon Mar 23 14:33:38 2015 [LCM][I]: New VM state is UNKNOWN
Mon Mar 23 14:37:58 2015 [VMM][I]: VM found again, state is RUNNING
Mon Mar 23 14:39:01 2015 [LCM][I]: New VM state is UNKNOWN
Mon Mar 23 15:00:33 2015 [VMM][I]: VM found again, state is RUNNING
Mon Mar 23 15:01:21 2015 [LCM][I]: New VM state is UNKNOWN
Mon Mar 23 15:04:06 2015 [VMM][I]: VM found again, state is RUNNING
Mon Mar 23 15:04:17 2015 [LCM][I]: New VM state is UNKNOWN
Mon Mar 23 15:15:43 2015 [VMM][I]: VM found again, state is RUNNING
Mon Mar 23 15:17:16 2015 [LCM][I]: New VM state is UNKNOWN
Mon Mar 23 15:19:59 2015 [VMM][I]: VM found again, state is RUNNING
Mon Mar 23 15:20:13 2015 [LCM][I]: New VM state is UNKNOWN
Mon Mar 23 15:27:49 2015 [VMM][I]: VM found again, state is RUNNING
Mon Mar 23 15:29:06 2015 [LCM][I]: New VM state is UNKNOWN
Mon Mar 23 15:32:25 2015 [VMM][I]: VM found again, state is RUNNING
Mon Mar 23 15:32:59 2015 [LCM][I]: New VM state is UNKNOWN
Mon Mar 23 15:40:11 2015 [VMM][I]: VM found again, state is RUNNING
Mon Mar 23 15:40:56 2015 [LCM][I]: New VM state is UNKNOWN
We fix a couple of issues related to the automatic VM state update with
monitor information through the 4.8-4.12 releases. I’ve checked the 4.6
code and the VM seems to be missing and found in each monitor interval. So
could you check that the VMs are where they are supposed to be (i.e. onhost
show list the correct VMs; onevm show list the correct hosts, etc…)?
Maybe you could try to run onedb fsck if you have the chance to stop oned.