关于 “VMware Workstation 不可恢复错误- (vcpu-0)”

解决VMwareWorkstation不可恢复错误
本文记录了重装系统后在VMwareWorkstation上创建虚拟机遇到的不可恢复错误,并通过查看日志文件逐步排查问题原因。最终确定解决方案为在BIOS中启用CPU虚拟化。

重装系统后第一次在 VMware Workstation 上创建虚拟机,结果出现了 VMware Workstation 不可恢复错误: (vcpu-0) 错误。

error

于是我们遵循它给出的提示,查看一下日志文件:

2017-06-16T20:36:19.904+08:00| vmx| I125: Log for VMware Workstation pid=6632 version=12.5.6 build=build-5528349 option=Release
2017-06-16T20:36:19.904+08:00| vmx| I125: The process is 64-bit.
2017-06-16T20:36:19.904+08:00| vmx| I125: Host codepage=windows-936 encoding=GBK
2017-06-16T20:36:19.904+08:00| vmx| I125: Host is Windows 10, 64-bit  (Build 15063)
2017-06-16T20:36:19.821+08:00| vmx| I125: VTHREAD initialize main thread 0 "vmx" host id 304
2017-06-16T20:36:19.821+08:00| vmx| I125: LOCALE GBK -> zh_CN User=804 System=804
2017-06-16T20:36:19.821+08:00| vmx| I125: Msg_SetLocaleEx: HostLocale=GBK UserLocale=zh_CN
2017-06-16T20:36:19.857+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.857+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware\VMware Workstation): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.857+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.857+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware\VMware Workstation): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.857+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.857+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware\VMware Workstation): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.873+08:00| vmx| I125: DictionaryLoad: Cannot open file "C:\Users\Default\AppData\Roaming\VMware\config.ini": The system cannot find the path specified.
2017-06-16T20:36:19.873+08:00| vmx| I125: Msg_Reset:
2017-06-16T20:36:19.873+08:00| vmx| I125: [msg.dictionary.load.openFailed] Cannot open file "C:\Users\Default\AppData\Roaming\VMware\config.ini": The system cannot find the path specified.
2017-06-16T20:36:19.873+08:00| vmx| I125: ----------------------------------------
2017-06-16T20:36:19.873+08:00| vmx| I125: ConfigDB: Failed to load C:\Users\Default\AppData\Roaming\VMware\config.ini
2017-06-16T20:36:19.873+08:00| vmx| I125: OBJLIB-LIB: Objlib initialized.
2017-06-16T20:36:19.873+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.873+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware\VMware Workstation): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.873+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.873+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware\VMware Workstation): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.873+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.873+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware\VMware Workstation): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.873+08:00| vmx| I125: DictionaryLoad: Cannot open file "C:\Users\Default\AppData\Roaming\VMware\config.ini": The system cannot find the path specified.
2017-06-16T20:36:19.873+08:00| vmx| I125: PREF Optional preferences file not found at C:\Users\Default\AppData\Roaming\VMware\config.ini. Using default values.
2017-06-16T20:36:19.873+08:00| vmx| I125: UUID: SMBIOS UUID is reported as '00 00 00 00 00 00 00 00-00 00 4c cc 6a f9 e8 35'.
2017-06-16T20:36:19.873+08:00| vmx| I125: FILE: FileLockDynaLink: Further process validation tools are: available
2017-06-16T20:36:19.873+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Users\Default\AppData\Roaming\VMware\preferences.ini.lck): The system cannot find the path specified (3)
2017-06-16T20:36:19.873+08:00| vmx| W115: FILE: FileLockCreateEntryDirectory creation failure on 'C:\Users\Default\AppData\Roaming\VMware\preferences.ini.lck': No such file or directory
2017-06-16T20:36:19.873+08:00| vmx| I125: Msg_Reset:
2017-06-16T20:36:19.873+08:00| vmx| I125: [msg.preference.loadNoLock] Unable to lock user preference file C:\Users\Default\AppData\Roaming\VMware\preferences.ini for reading.
2017-06-16T20:36:19.873+08:00| vmx| I125: ----------------------------------------
2017-06-16T20:36:19.873+08:00| vmx| I125: PREF Failed to load user preferences.
2017-06-16T20:36:19.904+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.904+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.904+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.904+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.904+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.904+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Users): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.904+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Users\Vince): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.904+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Users\Vince\AppData): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.904+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Users\Vince\AppData\Local): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.904+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Users\Vince\AppData\Local\Temp): Cannot create a file when that file already exists (183)
2017-06-16T20:36:19.904+08:00| vmx| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Users\Vince\AppData\Local\Temp\vmware-Vince): Cannot create a file when that file already exists (183)

[...]

2017-06-16T20:36:22.370+08:00| vcpu-0| I125: Msg_Post: Error
2017-06-16T20:36:22.370+08:00| vcpu-0| I125: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vcpu-0)
2017-06-16T20:36:22.370+08:00| vcpu-0| I125+ vcpu-0:VERIFY vmcore/vmm/main/cpuid.c:386 bugNr=1036521
2017-06-16T20:36:22.370+08:00| vcpu-0| I125: [msg.panic.haveLog] A log file is available in "D:\Virtual Machines\OpenSUSE\vmware.log".  
2017-06-16T20:36:22.370+08:00| vcpu-0| I125: [msg.panic.requestSupport.withoutLog] You can request support.  
2017-06-16T20:36:22.370+08:00| vcpu-0| I125: [msg.panic.requestSupport.vmSupport.windowsOrLinux] 
2017-06-16T20:36:22.370+08:00| vcpu-0| I125+ To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.
2017-06-16T20:36:22.370+08:00| vcpu-0| I125+ You can also run the "vm-support" script in the Workstation folder directly.
2017-06-16T20:36:22.370+08:00| vcpu-0| I125: [msg.panic.response] We will respond on the basis of your support entitlement.
2017-06-16T20:36:22.370+08:00| vcpu-0| I125: ----------------------------------------

。。。。。。

不能创建已存在的文件。。。

再次看一下错误提示: 可以直接在 Workstation 文件夹中运行“vm-support”脚本

我们来试一下:

cmd

发现多了一个 .zip 格式的压缩包,

zip.png

把它交给技术支持就行了。

然而这并没有什么用,于是我开启 google 大法,

有说关闭 Hyper-V 的,于是我试了一下:

Disable-WindowsOptionalFeature -Online -FeatureName:Microsoft-Hyper-V -All
  • 1

snipaste_20170616_210151.png

发现,还是不行。

有说,要在 BIOS 中开启 CPU VIRTUALIZATION,我试了一下这次终于成功了。

snipaste_20170616_213521.png

转载于:https://www.cnblogs.com/zhujiabin/p/9619934.html

<think>我们正在处理VMware Workstation中出现的"不可恢复错误(vcpu-0)"或"(vcpu-1) Exception 0xc0000005 (access violation)"错误。根据引用内容,我们可以总结出以下解决方案: 引用[1]和[3]提到错误信息为“Exception 0xc0000005 (access violation)”,这是一个内存访问冲突异常。引用[2]和[4]则提到错误信息包含“VERIFY vmcore/vmm”,这通常与虚拟机硬件版本过高有关。 结合引用内容,解决方案如下: 1. 降级虚拟机硬件版本(针对VERIFY vmcore/vmm错误)[引用2,4]: 关闭虚拟机,编辑.vmx文件,将virtualHW.version的值改为较低版本(例如从16改为10)。 2. 修复VMware安装(针对未知原因)[引用3]: 运行VMware安装程序,选择“修复”选项,或者通过控制面板的卸载程序中选择VMware进行修复。 3. 禁用Hyper-V(针对访问冲突): 在主机上以管理员身份运行命令提示符,执行命令:`bcdedit /set hypervisorlaunchtype off`,然后重启主机。 4. 调整虚拟机处理器设置: 在虚拟机设置中,尝试取消勾选“虚拟化Intel VT-x/AMD-V”和“虚拟化IOMMU”(注意:这可能会影响虚拟机性能,但有时可以解决兼容性问题)。 同时,减少虚拟机的CPU核心数(例如物理CPU有8核,则分配给虚拟机不超过4核)。 5. 检查主机BIOS/UEFI设置: 确保已启用CPU的虚拟化支持(Intel VT-x或AMD-V)。 6. 更新或回退VMware版本: 如果问题出现在升级VMware之后,可以尝试回退到之前的稳定版本。 7. 对于运行macOS的虚拟机: 使用Unlocker工具,并在.vmx文件中添加特定的配置行(如引用4所述)。 8. 检查内存问题: 异常0xc0000005可能是由主机或虚拟机内存问题引起。运行内存检测工具(如Windows内存诊断)检查主机内存。 9. 检查系统更新: 某些Windows更新可能与VMware冲突,尝试卸载最近的更新(特别是与Hyper-V相关的更新)。 现在,我们将这些解决方案组织成结构化的步骤,并生成相关问题。</think>针对 VMware Workstation 出现的 **"不可恢复错误: (vcpu-1) Exception 0xc0000005 (access violation)"** 问题,结合引用内容和实际解决方案,以下是系统性的解决步骤: --- ### **一、核心解决方案(按优先级排序)** #### 1. **修复 VMware 安装**(引用[3]关键方案) - 运行 VMware 安装程序 → 选择 **"修复"** 选项 - 或通过控制面板 → 卸载程序 → 双击 VMware → 选择修复 - 完成后重启主机再测试虚拟机[^3] #### 2. **降级虚拟机硬件版本**(引用[4]验证方案) ```diff # 关闭虚拟机后编辑 .vmx 文件 - virtualHW.version = "18" + virtualHW.version = "14" # 建议降至14或更低 ``` - 同时添加防崩溃参数(对 macOS 尤其有效): ```smc.version = "0" cpuid.0.eax = "0000:0000:0000:0000:0000:0000:0000:1011"``` [^4] #### 3. **禁用 Hyper-V 冲突** ```batch :: 管理员权限运行CMD bcdedit /set hypervisorlaunchtype off ``` - 重启后检查是否生效: ```systeminfo | findstr /I "Hyper-V"``` (应显示"未检测到 Hyper-V") #### 4. **内存访问冲突修复**(引用[1]针对性方案) - **虚拟机设置 → 内存**: - 将内存分配降至 **物理内存的 50% 以下** - 取消勾选 _"所有额外内存分配给虚拟机"_ - **主机系统**: - 运行内存诊断工具:`mdsched.exe` - 卸载最近安装的安全软件(特别是带有内存防护功能的)[^1] --- ### **二、进阶修复方案** #### 1. **CPU 虚拟化调整** | 设置项 | 推荐操作 | |-------------------------|----------------------------| | 虚拟化 Intel VT-x/AMD-V | ✅ 启用(BIOS和VM中同时开启) | | 虚拟化 IOMMU | ❌ 禁用 | | CPU 核心数 | ≤ 物理核心数的1/2 | | 虚拟化性能计数器 | ❌ 禁用 | #### 2. **日志分析与精准定位** 检查 `vmware.log` 中的关键错误模式: - `Exception 0xc0000005` → 内存冲突(降级硬件版本或减少内存) - `VERIFY vmcore/vmm` → 核心模块错误(修复VMware安装) - `EPT violation` → CPU虚拟化异常(更新BIOS微码) #### 3. **驱动与系统更新** - **关键驱动更新**: - 芯片组驱动(Intel/AMD官网最新版) - NVIDIA/AMD显卡驱动(使用 **Studio驱动** 而非Game Ready) - **VMware补丁**: 安装最新Workstation Pro补丁包([下载页](https://customerconnect.vmware.com/downloads/)) --- ### **三、特殊场景解决方案** #### 1. **Windows 11 主机** - 在 `.vmx` 文件中添加: ```monitor_control.restrict_backdoor = "TRUE"``` - 禁用内核隔离: 设置 → 隐私和安全性 → 设备安全性 → 内存完整性 → 关闭 #### 2. **macOS 虚拟机** - 使用 [Unlocker 4.3.2](https://github.com/DrDonk/unlocker/releases) - 执行: ```win-install.cmd```(需关闭VMware服务) #### 3. **Linux 虚拟机** - 内核参数调整: ```GRUB_CMDLINE_LINUX="noibrs noibpb nopti nospectre_v2 nospectre_v1"``` - 禁用3D加速: 虚拟机设置 → 显示器 → 取消"加速3D图形" --- ### **四、终极排查流程** ```mermaid graph TD A[发生 vcpu-1 错误] --> B{检查日志} B -->|VERIFY错误| C[修复VMware安装] B -->|0xc0000005| D[降级硬件版本] B -->|EPT错误| E[更新BIOS] C & D & E --> F[测试虚拟机] F -->|仍失败| G[新建空白虚拟机] G -->|成功| H[重建问题虚拟机] G -->|失败| I[硬件诊断] ``` > **重要提示**: > 若错误出现在 **Intel 12/13代 CPU** 或 **AMD Ryzen 7000系列**,需在BIOS中: > - 禁用 `CFG Lock` > - 禁用 `Overclocking Features` > - 启用 `SVM Mode`(AMD)/ `VT-x`(Intel) --- ### **相关问题** 1. 如何安全编辑 VMware 虚拟机的 `.vmx` 配置文件? 2. 修复 VMware 安装会丢失虚拟机数据吗? 3. 哪些 BIOS 设置对解决 vcpu 错误最关键? 4. 如何为 VMware 生成详细错误日志? 5. 虚拟机硬件版本降级有哪些风险? 6. Exception 0xc0000005 错误与物理内存故障如何区分? [^1]: VMware Workstation 不可恢复错误: (vcpu-1) Exception 0xc0000005 终极解决方案 [^2]: VMware Player 16 unrecoverable error vcpu-0 社区解决方案 [^3]: VMware 修复安装解决 vcpu-0 异常访问冲突 [^4]: Mac OS X Unlocker 文档中的硬件版本降级方案
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值