# Clarification on Windows VM Showing Fake Running State After Poweroff in OpenNebula

**URL:** <https://forum.opennebula.io/t/clarification-on-windows-vm-showing-fake-running-state-after-poweroff-in-opennebula/13796>\
**Category:** Product Support\
**Created:** [May 1, 2025, 6:19am UTC](https://forum.opennebula.io/t/clarification-on-windows-vm-showing-fake-running-state-after-poweroff-in-opennebula/13796 "2025-05-01T06:19:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nandakumar](https://avatars.discourse-cdn.com/v4/letter/n/58956e/32.png) [@Nandakumar](https://forum.opennebula.io/u/Nandakumar)\
**Post date:** [May 1, 2025, 6:19am UTC](https://forum.opennebula.io/t/clarification-on-windows-vm-showing-fake-running-state-after-poweroff-in-opennebula/13796/1 "2025-05-01T06:19:43Z")

</div>

HI,

I am encountering an issue with a Windows virtual machine managed by OpenNebula (Nebula platform).

After performing either a **hard or soft power off** , the VM correctly transitions to the **POWEROFF** state. However, after approximately 2 minutes, the VM unexpectedly transitions back to **RUNNING** state in the OpenNebula UI, although it is actually powered off. This state persists for around **10 minutes** , after which the VM status automatically corrects itself back to **POWEROFF**.

Here are the relevant log entries from `/var/log/one/245598.log`:

```auto
Thu May 1 09:06:12 2025 [Z0][VM][I]: New state is POWEROFF
Thu May 1 09:09:55 2025 [Z0][VMM][I]: VM found again by the drivers
Thu May 1 09:09:55 2025 [Z0][VM][I]: New state is ACTIVE
Thu May 1 09:09:55 2025 [Z0][VM][I]: New LCM state is RUNNING
Thu May 1 09:17:55 2025 [Z0][LCM][I]: VM running but monitor state is POWEROFF
Thu May 1 09:17:55 2025 [Z0][VM][I]: New state is POWEROFF

```

As observed, OpenNebula marks the VM as RUNNING even though:

- The VM is not present in `virsh list` on the host (i.e., it’s actually stopped).
- The monitoring later detects it as POWEROFF and updates the state correctly after ~10 minutes.

### Query:

Could you please clarify why OpenNebula shows the VM in a “fake running” state for several minutes after shutdown? Is this behavior related to the probe interval or caching mechanism in the monitoring drivers?

Any suggestions to **reduce this delay** or **prevent the temporary false state** would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![FrancJP](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/francjp/32/7690_2.png) [@FrancJP](https://forum.opennebula.io/u/FrancJP)\
**Post date:** [May 14, 2025, 10:25am UTC](https://forum.opennebula.io/t/clarification-on-windows-vm-showing-fake-running-state-after-poweroff-in-opennebula/13796/2 "2025-05-14T10:25:22Z")

</div>

Hello @Nandakumar,

Apologies for the late reply.

While I cannot cover all the doubts you have, I can suggest you some options to see if the issue can be solved:

- Adjust Monitoring Intervals
- Verify Monitoring Scripts
- Check for Caching Issues
- Review VM Shutdown Procedures
- Monitoring Driver Behavior

As a final comment, check your OpenNebula Version, sometimes these issues appears due to use an older or deprecated version of OpenNebula.

Cheers,