Operation inconsistent with current state vmware что делать

[Fix] “Operation Inconsistent with Current State” VMware Error

Have you ever got the “Operation inconsistent with current state” VMware error when you resume a suspended virtual machine on VMware Workstation, Fusion, or Player? What causes it and how to solve it? This article will answer these questions for you.

By Crystal / Updated on December 2, 2022

Share this:
Table of Contents

1. Case: The “Operation inconsistent with current state” VMware error
2. Solution to the “Operation inconsistent with current state” VMware error
3. Backup important file on Workstation VM to avoid accidental loss
4. Summary

Case: The “Operation inconsistent with current state” VMware error

Yesterday, I pressed the Suspend button of my VMware, which runs on Windows. This morning, when I press the Run button, I get the error message “Operation inconsistent with current state” mentioned in the header. My VMware version is Workstation 15 Pro 15.5.2 build 15785246. Between Suspend and Run, the PC has been rebooted. I am using Windows 10 Pro 10.0.18362 Build 18362. I am running Ubuntu inside the VMware.

I would like to hear your opinion as to what I should do?

— Question from stackoverflow.com

VMware Workstation is a popular type-2 hypervisor designed for end users and small businesses or organizations. It is a fairly straightforward and simple-to-use application that helps you to deploy many operating systems workloads and applications on a single server.

Many users create virtual machines (VMs) on VMware Workstation as lab environments to test software, updates, or even virus. And that makes for frequent crashes or errors. The “Operation inconsistent with current state” VMware error is one of them.

Have you also got the error? It occurs not only on VMware Workstation, but also on VMware Fusion or Player. So, what causes it and how to solve it? This article will provide the solution for you.

Solution to the “Operation inconsistent with current state” VMware error

The VMware “Operation inconsistent with current state” error often occurs when you start a suspended virtual machine on VMware Workstation, Fusion, or Player. In your current session, the virtual machine is suspended or closed, however, it remains in an open state in the VM services. This issue may be caused by improperly or forcibly shutting down the virtual machine. And therefore, resulting in the inconsistency.

The solution to the VMware Workstation “Operation inconsistent with current state” error is actually very simple. You only need to shut down the virtual machine and the VMware hypervisor properly, and then start the hypervisor and virtual machine as administrator.

Backup important file on Workstation VM to avoid accidental loss

You may get many unexpected errors while using virtual machines. If a virtual machine is not working properly, you may lose your important data on that VM. To prevent this issue from happening, it is necessary to back up the important data on these VMs.

By installing a backup agent on the guest operating system (OS) of the workstation virtual machine, you can backup it as it is a physical machine. Which means you can exclude insignificant applications and data from backups to reduce the size, and perform granular recovery when you only need some specific files urgently.

Furthermore, in this way you can also migrate all data on one virtual or physical machine to another, for example, convert VMware to Hyper-V or vice versa.

To backup VMware Workstation VMs more efficiently, here I will introduce you a professional backup software, AOMEI Centralized Backupper which can back up all windows systems.

Here is a 30-day free trial for you:

Secure Download

To properly using AOMEI Centralized Backupper to back up virtual or physical machines of multiple endpoints, you need follow these steps:

Attach an IP (better static) to the virtual machine you want to back up.

1. Launch AOMEI Centralized Backupper, and install ACB Agent remotely or manually on virtual or physical machines by clicking Computers > Install Client Program.

For the computers with client programs installed manually, you still need to Request Control over them for the further operation.

2. Click Computers > Uncontrolled Computers to find the correct IP of virtual or physical machines, then click Request Control on the upper bar. A prompt window will show on their interface, once all permission received you can start to back up them whenever you like.

3. Click Tasks on the upper bar, click New Task and select System Backup to create a new backup task. Follow the 2 steps in the prompt window.

4. Click Add Computers to find the correct IP of the virtual or physical machines you want to backup, you can select multiple of them. click OK.

5. Select a location as the destination path. you can click Add Storage in the prompt window to add a Share or NAS Device as a storage end.

Besides, click Settings you can set Encryption, Compression level, Splitting, Intelligent Sector, and VSS in the prompt window.

6. Click Schedule, you can manage the time and frequency to automatically back up virtual or physical machines.

7. Click Scheme, the oldest backup will be automatically deleted once a new one is created, which is space saving.

8. Then click Start Backup, you can choose Only create this task, or Create and execute the tasks.

Once created, tasks will show on Tasks page separately. You can Edit Backup or Restore by clicking Advanced on the upper right of the task.

Summary

Have you ever got the “Operation inconsistent with current state” VMware error when you resume a suspended virtual machine on VMware Workstation, Fusion, or Player? This issue happens may because the improper way you shut down the virtual machine or the hypervisor. You can try restart the hypervisor as administrator to solve it.

Virtual machines are error-prone. To protect the important data in them, you may need to backup them regularly. In this regard, AOMEI Centralized Backupper is an effective and flexible backup software for granular recovery.

Crystal is an editor from AOMEI Technology. She mainly writes articles about virtual machine. She is a positive young lady likes to share articles with peolpe. Off work she loves travelling and cooking which is wonderful for life.

Related Articles

(Full Guide) Free Virtual Machine Backup for VMware & Hyper-V

Virtual machine backup is a big concept that includes different backup options in different hypervisors which may confuse you. In this article, I will help you pick the right VMware or Hyper-V VM backup solution, and offers a step-by-step guide to backup virtual machine.

How to Convert or Move VMware Workstation VM to ESXi | 3 Ways

If you want to upgrade your environment from VMware Workstation to ESXi, you may also need to move Workstation VM to ESXi server. In this article, I will introduce you 3 methods.

The Selected Virtual Disk Is Incompatible with This Workstation

When using VMware Workstation to install macOS guest operating system on a Windows host machine, you may encounter the error “the selected virtual disk is incompatible with this Workstation”. How to fix it? This article covers 2 solutions to it.

How to Install ESXi 7.0 on VMware Workstation

Many users ask that if it is feasible to install VMware ESXi on desktop PC. Deploying a ESXi 7.0 in PC is affordable than using the dedicated product. Here offers the step-by-step post to install ESXi 7.0 om Workstation.

Free Get AOMEI Cyber Backup Now – Simple & Powerful

133M+ worldwide users 14 years data security experience

• Protect VMware, Hyper-V, Windows PCs & Servers and MSSQL Servers.
• Save backups to local path, network drive / NAS drive.
• Fast and granular recovery to minimize downtime.

VMware error «Unable to change power state of virtual machine UPS: Operation inconsistent with current state» [closed]

Closed. This question is not about programming or software development. It is not currently accepting answers.

This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.

Closed 10 months ago .

Yesterday, I pressed the Suspend button of my VMware, which runs on Windows. This morning, when I press the Run button, I get the error message mentioned in the header. My VMware version is Workstation 15 Pro 15.5.2 build 15785246 . Between Suspend and Run, the PC has been rebooted. I am using Windows 10 Pro 10.0.18362 Build 18362 . I am running Ubuntu inside the VMware. I searched the internet, found a post from 2017 that proposed that I run this command:

sudo /usr/bin/vmware-modconfig --console --install-all 

Since I am completely new to the subject, and I was only able to find one post about it, I would like to hear your opinion as to what I should do?

【无标题】VMware报错：Operation inconsistent with current state。

温温。 最新推荐文章于 2023-08-03 15:53:40 发布

阅读量166 收藏

点赞数

版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

VMware报错：Operation inconsistent with current state。错误解决方法
一般是因为网络问题或者是在打开VMware的时候打开了两次
解决方法：
关闭虚拟机，重新开启。

阅读终点，创作起航，您可以撰写心得或摘录文章要点写篇博文。去创作

觉得还不错? 一键收藏

知道了

【无标题】VMware报错：Operation inconsistent with current state。
VMware报错：Operation inconsistent with current state。
【vmware】Operation inconsistent with current state报错问题

09-14 305

vmware worlstation15.5 打开虚拟机报错 ：operation inconsistent with current state？

09-18 98

退出vm，重新以管理员身份启动vm，然后就能正常打开虚拟机了。
参与评论 您还未登录，请先 登录 后发表或查看评论
虚拟机打开时报错Operation inconsistent with current state

11-19 6269

文章目录问题描述导致原因解决方案 问题描述 Operation inconsistent with current state vmware 翻译：操作与当前状态不一致 导致原因 1.可能是因为上一次的虚拟机操作不当有关，比如关机不当， 2.虚拟机没有关好， 3.或者直接关闭虚拟机导致。 解决方案 快速方案：关闭vmware 软件重新启动虚拟机。 最后的办法，找到该虚拟机目录中的 .lck 后缀文件夹，将其删除后再尝试打开虚拟机。 .

VMware虚拟机 ——Operation inconsistent with current state。操作与当前状态不一致解决方法

12-04 6958

今天一打开VMware虚拟机 就跳出个界面，如下图 所示 ：Operation inconsistent with current state ，这句话的意思是操作与当前状态不一致。 我想着试试快走行不行，然后发现恢复快照会弹出图二的界面，上面写着：无法识别的设备：»PowerState«。 到底改怎么办呢，下面我来分享下我的解决办法。 1、我们首先通过按下键盘上的shift+ctrl+左上角的ESC，来打开任务管理器。 2、在最上面一排找到“服务”并点击，接着鼠标先随便点下面一.

vmware worlstation15.5 打开虚拟机报错 ：operation inconsistent with current state！

03-09 2844

解决方法一：以管理员身份重启虚拟机 解决方法二：重装虚拟机
vmware15中开启虚拟机出现Operation inconsistent with current state

03-08 6479

ubuntu虚拟机打不开，提示operation inconsistent with current state

07-13 4257

虚拟机出现Operation inconsistent with current state。操作与当前状态不一致解决方法

01-11 2529

虚拟机出现Operation inconsistent with current state。操作与当前状态不一致解决方法
虚拟机报错：Operation inconsistent with current state.

08-04 1178

我安装的是ubuntu16.04版本，多次开机都出现了这个错误。有的时候可以继续用，有的时候需要重启。在网上找了很多方法，比如说以管理员的权限启动、删除ub文件夹中的后缀为lck的文件等等，都没有实际的效果。 之后我总结一些规律，解决了这一问题： 第一点是不要多次开虚拟机； 第二点是关机的时候一定要正常关机； 第三点就是要单击Ubuntu，不要双击。 希望可以帮助到和我有一样烦恼的同学们 .

在虚拟机中报错Operation inconsistent with current state

11-25 913

在虚拟机中出现这个错误 Operation inconsistent with current state 如果之前虚拟机是挂机状态，然后继续运行 后出现这样的错误。 方法一：重启虚拟机，看看网页是否是一次性打开了多个虚拟机，关闭再重启 方法二：如果是vm15，先退出，然后用管理员权限运行，点开就能正常启动。退出>管理员权限>点开需要开启的虚拟机。 （网上网友评论，可以尝试一下） .

关于VMware中安装Ubuntu18.04.4设置静态ip以及apt换源的问题与解决

最近开始学着使用Ubuntu操作系统 有着安装CentOS的经验，本安装过程会很简单，但发现还是有好多地方不一样的，甚至想骂娘，o(╥﹏╥)o。 本篇作为整理，中间详细步骤就不列出 主要问题在apt换源、设置静态ip（网上关于虚拟机中ip设置直接在更改虚拟机网络编辑器中设置还原默认设置，当然这也可以，但我因为一些原因得设置静态ip） 设置静态ip： 查看虚拟机网络编辑器中 子网ip、子网掩码、网关ip 修改 /etc/hosts 文件： localhost前面的ip不用改不用注释，hostname前面的ip地址改为自己想要设置的ip，hostname在/etc/hostname更改 修改

《Thinking in C++》(Second Edition)书中代码
Bruce Eckel的力作《Thinking in C++》(Second Edition)书中代码
解决打开虚拟机报错Operation inconsistent with current state问题

08-11 1万+

打开虚拟机VMware Workstation报错 Operation inconsistent with current state问题 解决方法：先退出VMware Workstation，然后右键管理员权限运行即可正常打开Ubuntu。

虚拟机打开时报错Operation inconsistent with current state。

05-23 6166

虚拟机报错Operation inconsistent with current state。 有时候突然打开虚拟机会出现这个状况 我看过很多博客，也用过很多方法，下面根据自身经验给大家介绍一下怎么解决这个问题。 出现这个问题很可能是因为你上次虚拟机没有关好，直接关闭VMWare或者直接关机。 解决方法： 一、大家可以尝试重启虚拟机。 二、如果直接重启虚拟机没有效果，试一下关闭杀毒软件再尝试重启虚拟机。 三、最后的办法，找到该虚拟机目录中的 .lck 后缀文件夹，将其删除后再尝试打开虚拟机。 大家一点要用正

启动虚拟机报错：Operation inconsistent with current state

08-03 30

2、找到该虚拟机目录中的 .lck 后缀文件夹，将其删除后再尝试打开虚拟机。（1）没有正常退出项目，直接关闭虚拟机。（2）虚拟机还没有关闭，就直接关闭电脑。1、重新启动VMware。
Installation failed with message Failed to finalize session : INSTALL_FAILED_INVALID_APK: /data/app/

一直正常运行的项目这次运行时出现了： Installation failed with message Failed to finalize session : INSTALL_FAILED_INVALID_APK: /data/app/vmdl890369339.tmp/7_slice__ signatures are inconsistent. It is possible that this issue is resolved by uninstalling an existing version of the apk if it is present, and then re-ins

Consistent Query Answering Based on Repairing Inconsistent Attributes with Nulls
Consistent Query Answering Based on Repairing Inconsistent Attributes with Nulls
【虚拟机】解决“operation inconsistent with current state”

12-24 224

vmware workstation打开每个虚拟机都提示 operation inconsistent with current state,请问如何处理？
Dealing with inconsistent secure messages by weighting majority

Messages transmitted between senders and receivers might be inconsistent owing to potential communication block, message lost and/or malicious attacks, in electronic commerce. And current formal methods for security protocol analysis show limitations in handling the incoherent secure messages that may be derived from different sources or at different moments. This results in increasing risk of e-commerce activities. This paper thus proposes a formal framework to deal with the inconsistency in se

operation inconsistent with current state

«operation inconsistent with current state» 这个错误提示通常是指当前的操作与系统或程序的当前状态不一致，可能由于之前的某些操作或程序错误导致了系统或程序的异常状态，从而导致了这个错误。要解决这个问题，通常需要查看具体的错误信息或日志，找出导致异常状态的原因，并对其进行修复。可能需要重启系统或程序，或者对系统或程序进行更新或升级，以恢复其正常状态。

Fix VMware Error: Virtual Machine Disks Consolidation Needed

Virtual machines in VMware vSphere have many advantages. They work reliably with high performance if the appropriate hardware is used and the right software configuration is applied. Sometimes the virtual machine consolidation needed status is displayed in the VMware vSphere Client, and a system administrator has to fix this error. This blog post explains why VMware virtual machine disks consolidation is needed and how this error can be fixed.

NAKIVO for VMware vSphere Backup

Complete data protection for VMware vSphere VMs and instant recovery options. Secure backup targets onsite, offsite and in the cloud. Anti-ransomware features.

What Is VMware Disk Consolidation?

Virtual disk consolidation is the process of merging virtual disk files created after taking VM snapshots. You can initiate disk consolidation on demand to avoid performance degradation and other issues. When you take a snapshot, delta disks are created and changes are written to the appropriate delta disk (the latest delta disk by default, until one of the previous snapshots is selected to restore the virtual machine). As a result, redundant data is present in the virtual machine storage because each delta disk contains all changes made as compared to the previous delta disk state, and the parent disk remains unchanged.

When the chain of snapshots and related virtual disk files becomes large, performance degrades. When you perform VMware disk consolidation, data from delta disks is merged to a single disk, and no redundant data is left on the datastore where this VM’s files are located. Storage space is cleaned after you consolidate virtual machine disk files. Remember that VMware recommends using no more than 32 snapshots per VM.

Possible Reasons for the VMware Disk Consolidation Error

The VMware virtual machine disks consolidation is needed error message is displayed in the VM Summary tab in the VMware vSphere Client (screenshot below). One of the common reasons for this error message is incorrectly deleting a VM snapshot, which can leave VMDK files related to snapshots and log files on the datastore (for example, after you performed the Delete All or Delete operation for VM snapshots).

The most common causes for the virtual machine consolidation needed status:

• Not enough disk space on the VMFS datastore to consolidate VM snapshots and consolidate virtual disk files. If there is less than 1 GB of free space on the datastore, this error may occur.
• Low performance of a storage system attached to an ESXi host on which a VM is running. If the snapshot size is large or times out, snapshot consolidation can fail.
• Connection issues between an ESXi host and vCenter.
• Snapshot files are locked by a third-party application, for example, a backup application. This may occur if a backup application did not finish a backup job and locked the snapshot (backup applications can create a temporary snapshot of a virtual machine when running a backup). Backup applications are unable to quiesce disk without using snapshot techniques to make a consistent backup of a running VM.

Basically, you should restore the consistency of VM disk files.

How to Fix the Error?

To fix the virtual machine consolidation needed status, right click the VM name in the VMware vSphere Client and in the menu that opens, click Snapshots > Consolidate.

A confirmation message is displayed:

This operation consolidates all redundant redo logs on your virtual machine. Are you sure you want to continue?

Click Yes to confirm and consolidate virtual machine disk files.

Note: If there is a concern that some data can be lost during VMware disk consolidation, make a VMware VM backup, for example, copy all VM files to another folder on a datastore and then perform VMware disk consolidation.

Wait until the VMware disk consolidation is complete and the logs are cleared. You can see the task progress in the task panel at the bottom of the VMware vSphere Client interface. If the VM is running, VM performance can degrade during this operation. The time needed to finish this operation depends on the VM size, the number of snapshots, and VM load.

After the VMware disk consolidation task is finished, the warning that VMware virtual machine disks consolidation is needed should disappear.

Errors that May Occur

Sometimes, another error can occur during VMware disk consolidation and the following error message is displayed:

Unable to access file since it is locked. An error occurred while consolidating disks: Failed to lock the file. Consolidation failed for disk node ‘scsi0:0’.

Locks can be also created when backup applications use the hot-add disk option for a backup when using snapshots. The VM file lock is intended to avoid concurrent writes to the file by multiple ESXi hosts.

Try to perform the following actions to fix this error.

1. Restart management agents on the ESXi server on which the VM resides. Open ESXi shell or connect to the ESXi host via SSH and run the command as root:

You can also open the ESXi direct console, go to Troubleshooting Options, and select Restart Management Agents (press Enter to activate the needed option, then press F11 to confirm).

1. Check the locked file with the command:

vmfsfilelockinfo -p /vmfs/volumes/vm_datastore/vm_name/vm_name.vmx

1. Check the hostd log file if you need to identify the path on the datastore where the VM files are located.

cat /var/log/hostd.log |grep -i vm_name

1. Go to the VM directory on the datastore when you know the VM files’ location:

1. Run the command to list ESXi hosts that are locking the VM files:

for i in `ls`; do vmfsfilelockinfo -p $i ;done|grep ‘is locked in\|Host owning the lock\|Total time taken’ | sed ‘s|Host owning the lock on file is||g’|sed ‘s|Total time|—|g’ | awk » |uniq

1. Restart ESXi management agents, including hostd and vpxa as explained above, or run these commands on the ESXi host locking the VM files:

Another method to unlock VM files

As an alternative, try these steps to fix an error occurred while consolidating disks: Failed to lock the file.

1. Shut down the virtual machine.
2. Take a new VM disk snapshot.
3. Delete all existing VM snapshots. Right click the VM name in vSphere Client, select Snapshots, and click Delete All Snapshots.

1. Clone the VM or migrate the VM to another ESXi host with vMotion if the error has not been fixed yet.
2. Try to consolidate snapshots once again, as explained above.

If these actions didn’t help, try to shut down the VM, open VM settings, select the VM options tab, then expand the Advanced section, and click Edit Configuration. In the Configuration parameters window, click Add Configuration Params. Add the asyncConsolidate.forceSync parameter and set this parameter to TRUE.

Sometimes the virtual machine consolidation needed status can be caused by inconsistent -ctk.vmdk files that are created for changed block tracking (by VM backup software, for example). Try to delete CTK files. They are not needed for snapshot consolidation. Don’t forget to back up VM files before deleting CTK files. Then try to consolidate virtual machine disk files again.

The Consolidate option is inactive

If the VMware consolidate snapshot option is greyed out (inactive), an active task can be running on the VM now. If you see the “detected an invalid snapshot configuration” error, some snapshots can be broken or there are split-chains of snapshots. In this case, try to do the following actions.

1. Connect to the ESXi server via SSH and go to the directory where the VM files are located on the datastore.

You can check the VM files’ location in the VMware vSphere Client and find the location of virtual disks by viewing VM settings.

1. Identify what disk snapshots are being pointed:

cat VM-name.vmx | grep scsi*

See the output to check virtual disk files including virtual disk snapshot files. For example, the name of the virtual disk file is displayed in the line. This is not a snapshot:

scsi 0:0.fileName = “VM-Name.vmdk”

In the output line, the name of the virtual disk snapshot file is displayed, and you are pointing the snapshot:

scsi 0:0.fileName = “VM-Name-000002.vmdk”

A SCSI virtual disk controller is used in VM configuration in this example.

1. The next command checks what each snapshot is pointing to. Use this command to detect which snapshot is pointing to the next disk file (the snapshot vmdk file or a base disk vmdk file) in the snapshot chain.

cat VM-Name-000002.vmdk | grep parentFileNameHint

You may need to execute this command again for other vmdk files (like VM-Name-000001.vmdk in this example) until you find the needed base disk. This method helps you find the inconsistency.

1. If you have found the inconsistency, for example, VM-Name-000002.vmdk is pointing to VM-Name-000001.vmdk which is pointing to VM-Name.vmdk, run vmkfstools on the highest point of the disk snapshot chain (VM-Name-000002.vmdk in this case):

vmkfstools -q -v10 VM-Name-000002.vmdk

This command tries to open and close all vmdk files in the chain and notifies you where failure occurs.

Using PowerCLI

As an alternative to executing VMware disk consolidation in the VMware vSphere Client graphical user interface, you can use vSphere PowerCLI with the command line interface.

1. Connect to the vCenter Server that manages the ESXi host with the VM that has the virtual machine consolidation needed status. Enter credentials when prompted.

Connect-VIServer vcenter01.test.com

1. Get the list of VMs with the virtual machine consolidation needed status:

1. Perform VMware disk consolidation.

Conclusion

This blog post has explained recommendations that can help you fix the virtual machine consolidation needed status. VMware virtual machine disks consolidation is usually needed when one of the snapshots is corrupted, a snapshot chain is inconsistent, or a snapshot is locked by another ESXi host.

Regularly run a VM backup in your VMware vSphere environment. If you have data backup, you can restore the data and resume working if data is deleted, corrupted, encrypted by ransomware or if you see an error occurred during vCenter operation. The VMware vCenter Server should be backed up, just like other important VMs. Consider using NAKIVO Backup & Replication – professional backup product that supports backing up virtual machines in VMware vSphere.

1 Year of Free Data Protection: NAKIVO Backup & Replication

Deploy in 2 minutes and protect virtual, cloud, physical and SaaS data. Backup, replication, instant recovery options.