26、在 vCenter Server 升级到 5.0 版本后,ESX 4.0 Update 2 主机可能崩溃
解决方法:发生崩溃时,同时在紫色屏幕上显示以下消息:NOT_IMPLEMENTED bora/vmkernel/filesystems/visorfs/visorfsObj.c:3391。
解决办法:升级到 vCenter Server 5.0 之前,将由 vCenter Server 管理的所有 ESX 4.0 Update 2 主机升级到 ESX 4.0 Update 3。
27、HA配置到90%时失败,提示:Internal AAM Error-agent could not start
故障状态:
1、第一台主机加入到Cluster没问题,但是第二台主机加入到cluster时,走到90%出错,提示如下错误:Internal AAM Errors-agent could not start
复制代码
2、在aam_config_util_addnode.log文件里有类似如下错误信息:
01.01/23/10 16:20:49 [myexit ] Failure location:
02.01/23/10 16:20:49 [myexit ] function main::myexit called from line 2199
03.01/23/10 16:20:49 [myexit ] function main::start_agent called from line 1168
04.01/23/10 16:20:49 [myexit ] function main::add_aam_node called from line 171
05.01/23/10 16:20:49 [myexit ] VMwareresult=failure
故障分析:
这种故障一般和UDP 8043端口无法访问有一定关系;
解决方案:
确保UDP 8043端口畅通无阻,比如:
执行如下命令:
tcpdump -i vswif0 -s 900 -n udp port 8043 -w ${主机名}.pcap
28、查阅和重装VirtualCenter Server agents(vpxa)服务
故障状态:
·配置VMware High Availability (HA) 失败;
·重新配置 VMware HA时,提示如下错误:
Could not Enable aam firewall ruleset :vim.fault.HostConfigFault
·无法将ESX添加到VirtualCenter;
·尝试重新将ESX添加到VirtualCenter时,提示如下错误:
unable to access the specified host, either it doesn't exist, the server software is not responding, or there is a network problem
·在hostd.log文件中有如下内容:
[2010-05-24 10:45:51.463 'Vmomi' 15752112 info] Throw vim.fault.AlreadyExists
[2008-05-26 10:45:51.463 'Vmomi' 15752112 info] Result:
(vim.fault.AlreadyExists) {
name = "vpxuser"
msg = ""
}
解决方案;
备注:当看到如下错误时,请在ESX主机上重装vpxa:
unable to access the specified host, either it doesn't exist, the server software is not responding, or there is a network problem.
查看安装在ESX/ESXi服务器上的VirtualCenter agent(vpxa)版本号的方法如下:
1.首先确定VirtualCenter的版本号:点击Help按钮,点击About可查阅;
命令查看VMware-vpxa的命令:
rpm -V VMware-vpxa
31、为主机应用Host Profiles提示compliance错误
故障状态:
为主机应用Host Profiles失败,提示如下错误:
01.Specification state absent from host: device '<datastore>' state needs to be set to 'on'
02.Host state doesn't match specification: device '<datastore>' needs to be reset
03.Specification state absent from host: device '<datastore>' Path Selection Policy needs to be set to 'VMW_PSP_FIXED'
04.Host state doesn't match specification: device '<datastore>' Path Selection Policy needs to be set to default for claiming SATP
故障分析:
这是由于PSA组件导致的;
解决方案:
1、右击Host Profiles后点击Enable/Disable Profiles配置选项;
2、展开“Storage Configuration”选项,展开“Pluggable Storage Architecture”这个uxanxiang;
3、去掉“PSA Device Configuration”;
4、展开“Native Muti-Pathing(NMP)”这个选项后,接着展开“PSP and SATP configuration for NMP devi”选项;
5、去掉“PSP configuration for”这个选项后点击OK即可。
34、丢失或锁定文档导致虚拟机无法Power On
故障状态:
1、虚拟机无法开启;
2、尝试开启虚拟机时,看到类似如下错误信息:
·Unable to open Swap File;
·Unable to access a file since it is locked;
·Unable to access Virtual machine configuration;
3、在/var/log/vmkernel文件里可以看到类似如下信息:
WARNING: World: VM xxxx: xxx: Failed to open swap file <path>ock was not free
WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>
4、当尝试开启虚拟机的console控制台时,可能会收到如下错误信息:
Error connecting to <path><virtual machine>.vmx because the VMX is not started
5、在开启虚拟机时,卡在95%位置无响应;
6、从模板部署一台新的VM之后无法开启虚拟机;
7、虚拟机在vCenter Server和ESXi/ESX主机之间报告控制台电源状态冲突;
故障分析:
导致这个问题的因素可能很多,但是众多问题中,都穿插或包含着文件损坏或文件被锁定等问题的可能。虚拟机常用的文件包括:
·*.vswp
·*-flat.vmdk
·*-delta.vmdk
·*.vmx
·*.log
解决方案:
首先需要确认哪些文件处于锁定状态:
1、利用vSphere Client登录ESXi/ESX主机、vCenter Server主机;
2、在Datastore里找到想要开启但是无法开启的虚拟机所在位置;
3、尝试开启虚拟机,如果无法开启且console显示错误,先查阅vmware.log日志文件的相关信息来确认问题;
4、利用SSH或COS选用root权限登录到ESXi/ESX主机之后执行下面的命令查看虚拟机的完整路径:
#vmware-cmd -l
系统将输出类似如下信息来显示注册到ESXi/ESX主机的虚拟机:
/vmfs/volumes/<UUID>/<虚拟机目录>/<虚拟机名>.vmx
5、执行下列命令切入到这个虚拟机所在的目录:
#cd /vmfs/voluems/<UUID>/<虚拟机目录>
6、然后查阅vmware.log日志,在文件的尾部查看什么原因导致这个问题后再针对性的分析。
35、Storage vMotion失败:looking for lines staring with "CBTMotion"
故障状态:
1、执行Storage vMotion失败;
2、系统提示如下错误信息:
01.A general system error occurred: Storage VMotion failed to copy one or more of the VM's disks. Please consult the VM's log for more details, looking for lines starting with "CBTMotion-".
复制代码3、/var/log/vmware/hostd.log文件里有类似如下信息:
01.Failed with error 340983807: Storage VMotion failed to copy one or more of the VM's disks. Please consult the VM's log for more details, looking for lines starting with "CBTMotion".
复制代码故障分析
可能由于虚拟机的硬件版本号过老导致;
解决方案:
关掉虚拟机后右击uxniji选择Upgrade Virtual Machine Hardware即可。