VM running but monitor state is POWEROFF

Community Support
1

Hello,

I am using OpenNebula 5.2 and KVM hypervisor. I have a problem with Windows machine regarding RUNNING/POWEROFF state. VM is running Windows 2k12 and auto POWEROFF. From VM log I saw the error message is “VM running but monitor state is POWEROFF”. I don’t kown why VM auto shutdown and move to POWEROFF state. What could be the reason for causing this issue?

Thu Dec 1 11:56:30 2016 [Z0][VMM][I]: ExitCode: 0
Thu Dec 1 11:56:30 2016 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Thu Dec 1 11:56:30 2016 [Z0][VMM][I]: ExitCode: 0
Thu Dec 1 11:56:30 2016 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy.
Thu Dec 1 11:56:31 2016 [Z0][VMM][I]: ExitCode: 0
Thu Dec 1 11:56:31 2016 [Z0][VMM][I]: Successfully execute network driver operation: post.
Thu Dec 1 11:56:31 2016 [Z0][VM][I]: New LCM state is RUNNING
Thu Dec 1 12:57:27 2016 [Z0][LCM][I]: VM running but monitor state is POWEROFF
Thu Dec 1 12:57:27 2016 [Z0][VM][I]: New LCM state is SHUTDOWN_POWEROFF
Thu Dec 1 12:57:27 2016 [Z0][VM][I]: New state is POWEROFF
Thu Dec 1 12:57:27 2016 [Z0][VM][I]: New LCM state is LCM_INIT
Thu Dec 1 12:57:53 2016 [Z0][VM][I]: New state is ACTIVE
Thu Dec 1 12:57:53 2016 [Z0][VM][I]: New LCM state is BOOT_POWEROFF
Thu Dec 1 12:57:53 2016 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/120/deployment.5
Thu Dec 1 12:57:53 2016 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Thu Dec 1 12:57:54 2016 [Z0][VMM][I]: ExitCode: 0
Thu Dec 1 12:57:54 2016 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Thu Dec 1 12:57:54 2016 [Z0][VMM][I]: ExitCode: 0
Thu Dec 1 12:57:54 2016 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy.
Thu Dec 1 12:57:55 2016 [Z0][VMM][I]: ExitCode: 0
Thu Dec 1 12:57:55 2016 [Z0][VMM][I]: Successfully execute network driver operation: post.
Thu Dec 1 12:57:55 2016 [Z0][VM][I]: New LCM state is RUNNING

2

Hi vynt!
Though some days have passed and you may have found a solution, I guess that the VM is indeed running in your KVM hypervisor but the monitor driver is having problems to get monitoring information. OpenNebula then assumes that it’s in the POWEROFF state according to the " VM running but monitor state is POWEROFF". I think you could try to check it there’s an issue with the monitor for that VM.

Could you paste the output of the following command (run it as oneadmin user) when you encounter that issue?

onevm show 120 -x (120 is the VM_ID according to your logs)

You may also try to run the following command:

/var/tmp/one/vmm/kvm/poll deploy_id

where deploy_id is an attribute assigned to your VM that you may find in the onevm show 120 output.

Finally you could also check the /var/log/one/oned.log and try to find errors that may be related.

Cheers!

1 Like
3

Hi mcabreizo,

Thank you for your reply. I fixed this issue by backup VM and delete-create new VM. Everything work ok.

4

Hello everyone,

I’m facing the same problem, after 7 minutes vm state turn to poweroff.

Is an ip address mandatory for monitor state to run correctly ?

I’m deploying vms without ip for test purpose.

Thank you !

5

There is the logs

Tue Jul 16 15:10:31 2019 [Z0][VM][I]: New LCM state is RUNNING
Tue Jul 16 15:17:08 2019 [Z0][LCM][I]: VM running but monitor state is POWEROFF
Tue Jul 16 15:17:08 2019 [Z0][VM][I]: New LCM state is SHUTDOWN_POWEROFF
Tue Jul 16 15:17:08 2019 [Z0][VM][I]: New state is POWEROFF
Tue Jul 16 15:17:08 2019 [Z0][VM][I]: New LCM state is LCM_INIT