免责声明:本文为 Powering on a virtual machine fails with the error: A general system error occurred (1006232) 的翻译版本。尽管我们会不断努力为本文提供最佳翻译版本,但本地化的内容可能会过时。有关最新内容,请参见英文版本。
A general system error occurred. The system returned on error. Communication with the virtual machine may have been interrupted
。Heap worldGroup<ID> could not be grown by 65536 bytes for allocation of 12288 bytes
An unexpected error was received from the ESX host while powering on VM vm-name
Failed to power on VM
Could not power on VM : Out of memory
services.sh
,您可能会看到以下错误:Component sfcb-ProviderMa not running, Restarting sfcbd.
/etc/init.d/sfcbd: line 38: cannot fork
/sbin/esxcfg-advcfg: error while loading shared libraries: libvmkctl.so: failed to map segment from shared object: Error 28
/etc/init.d/sfcbd-watchdog: line 455: cannot fork
.vmx
文件已损坏。.vmx
文件,请执行以下操作:.vmx
文件并编辑新文件。如果虚拟机的操作系统许可方案受 MAC 地址更改的影响,则可能需要执行上述操作。查找类似于以下格式的行:ethernetN.address = "xx:xx:xx:xx:xx:xx"
hostd
进程类似。有关详细信息,请参见 Restarting the Management agents on an ESXi or ESX host (1003490)。vmware-vim-cmd vmsvc/getallvms
(请注意虚拟机的 vmid
)
vmware-vim-cmd vmsvc/reload vmid
在 ESXi 上,请用 vim-cmd
替换 vmware-vim-cmd
。
注意:如果在尝试执行了本文中的步骤后问题仍然存在,请执行以下操作:
如果仍然无法打开虚拟机电源,请检查虚拟机自身的内存预留:
注意: 有关资源池的详细信息,请参见 vCenter Server and Host Management Guide。