# Windows VM showing fake running

**URL:** <https://forum.opennebula.io/t/windows-vm-showing-fake-running/13795>\
**Category:** Product Support\
**Created:** [May 1, 2025, 4:37am UTC](https://forum.opennebula.io/t/windows-vm-showing-fake-running/13795 "2025-05-01T04:37:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Senthil\_Kumar\_M](https://avatars.discourse-cdn.com/v4/letter/s/4bbf92/32.png) [@Senthil\_Kumar\_M](https://forum.opennebula.io/u/Senthil_Kumar_M)\
**Post date:** [May 1, 2025, 4:37am UTC](https://forum.opennebula.io/t/windows-vm-showing-fake-running/13795/1 "2025-05-01T04:37:12Z")

</div>

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:

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 KVM 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:19am UTC](https://forum.opennebula.io/t/windows-vm-showing-fake-running/13795/2 "2025-05-14T10:19:18Z")

</div>

Hello @Senthil_Kumar_M,

Apologies for the late reply.

When a VM is powered off, OpenNebula relies on its monitoring probes to update the VM’s state. If the monitoring interval is set to a longer duration, there can be a delay before OpenNebula recognizes that the VM is no longer running. This delay can cause the VM to temporarily appear as “RUNNING” even though it’s stopped.

To address this, I suggest you to do the following:

- Adjust Monitoring Interval
- Verify Monitoring Scripts
- Check for Caching Issues

Let me know if you need a technical reply for this.

Regards,

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/1/14d66f1130b9cd292905f575da9b68a9f574dd03.png) [@system](https://forum.opennebula.io/u/system)\
**Post date:** [June 25, 2025, 3:47pm UTC](https://forum.opennebula.io/t/windows-vm-showing-fake-running/13795/3 "2025-06-25T15:47:01Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.