This works great and fast. This is the ticket for me. Thanks!
Right as I saw your response I was toying with this. It takes a lot longer and it does not have the much better formatting of yours.
$vms = gc .\_VMs.txt
foreach($vm in $vms) {
get-vm $VM | get-vmhost | select name
}
Hello , I still have the same issue, for example, today the host CPU usage reached 100% (with 8 x 2.659Ghz) before getting completely blocked, and the only way was restart the server from the DRAC:
Could be fixed with an upgrade or patch ??:
My current ESXI version is:
~ # vmware -vl
VMware ESXi 5.5.0 build-2068190
VMware ESXi 5.5.0 Update 2
And my VCenter is: Version 5.5.0 Build 1300321
Regards.
Dear All,
My esxi 5.5 has a quetion like this:
I have tried turn off the power supply 1,the host still work
when I back power 1 and turned off the power supply 2, the host still work too
but alert could not solve
please help me
thanks
Hi Matt,
thanks for your help.
I will try to IPv6 disabled first.
thank you.
Try to update or reset sensors on "Hardware Status" tab in vCenter.
Or run the below command on your ESXi: services.sh restart
Just received confirmation from local h/w vendor, that this is known issue. It false alarm, and it can be ignored
Yes, restart all VDP appliances solved this problem.
Thanx.
I see that you can do this at the storage cluster level, Virtual machine settings and select the VM, select disabled but the VM still does a storage vMotion the next day after. We have storage DRS set up with a manual and automated schedule. The automated schedule seems to override the disabled VM setting.
Curious if anyone else has seen this. I enable HA on the cluster and I have a host that won't join HA, the error comes out as HA is unavailable. Checking the fdm log I see the below error.
Its not like normal SSL errors where the cert is bad, the problem is the new cert is good its just not being accepted. For the peer thumbprint it shows the thumbprint of the new cert, for the expectedthumbprint it shows the old cert. For whatever reason it just won't look for the new one even though the cert is perfectly fine. Any way to force vCenter to look for the new one? Its like its just not registering for some reason.
I've done all the basic stuff like remove it from the cluster and add it back in. Restart it, restart management agents. I even emptied the cluster out completly and added everything back, same answer.
2016-09-29T21:26:39.307Z [FFE46B70 verbose 'Cluster' opID=SWI-58bbb19f] [ClusterManagerImpl::AddBadIP] IP HA_MASTER_IP marked bad for reason Unreachable IP
2016-09-29T21:26:39.307Z [FFE46B70 info 'Message' opID=SWI-58bbb19f] Destroying connection
2016-09-29T21:26:39.317Z [FFF09B70 error 'Message' opID=SWI-586358c] [MsgConnectionImpl::FinishSSLConnect] Error N7Vmacore3Ssl18SSLVerifyExceptionE(SSL Exception: Verification parameters:
--> PeerThumbprint: NEW_THUMBRPINT
--> ExpectedThumbprint: OLD_THUMBPRINT
--> ExpectedPeerName: host-57
--> The remote host certificate has these problems:
-->
--> * Host name does not match the subject name(s) in certificate.
-->
--> * unable to get local issuer certificate) on handshake
2016-09-29T21:26:39.317Z [FFF09B70 warning 'Election' opID=SWI-586358c] [MasterVerificationInfo::ConnectComplete] Failed to connect to master host-57
2016-09-29T21:26:39.317Z [FFF09B70 verbose 'Election' opID=SWI-586358c] [ClusterElection::AddInvalidMaster] Added invalid master host-57
2016-09-29T21:26:39.317Z [FFF09B70 warning 'Election' opID=SWI-586358c] [ClusterElection::UpdateInvalidMasterCountMap] Host host-57 has been declared invalid 21 times
2016-09-29T21:26:39.317Z [FFF09B70 info 'Message' opID=SWI-586358c] Destroying connection
2016-09-29T21:26:40.295Z [FFCC1B70 verbose 'Cluster' opID=SWI-6058ed8] [ClusterManagerImpl::IsBadIP] HA_MASTER_IP is bad ip
2016-09-29T21:26:40.295Z [FFCC1B70 verbose 'Election' opID=SWI-6058ed8] CheckVersion: Version[2] Other host GT : 59261 > 0
2016-09-29T21:26:40.295Z [FFCC1B70 verbose 'Cluster' opID=SWI-6058ed8] [ClusterPersistence::VersionChange] version[2] 59261 from host-57,HA_MASTER_IP
2016-09-29T21:26:40.295Z [FFCC1B70 info 'Cluster' opID=SWI-6058ed8] [ClusterPersistence::VersionChange] fetching version[2] 59261 from host-57,HA_MASTER_IP
2016-09-29T21:26:40.295Z [FFCC1B70 verbose 'Cluster' opID=SWI-6058ed8] [ClusterManagerImpl::IsBadIP] HA_MASTER_IP is bad ip
2016-09-29T21:26:40.295Z [FFCC1B70 verbose 'Election' opID=SWI-6058ed8] CheckVersion: Version[2] Other host GT : 59261 > 0
2016-09-29T21:26:40.295Z [FFCC1B70 verbose 'Cluster' opID=SWI-6058ed8] [ClusterPersistence::VersionChange] version[2] 59261 from host-57,HA_MASTER_IP
2016-09-29T21:26:40.295Z [FFCC1B70 verbose 'Cluster' opID=SWI-6058ed8] [ClusterPersistence::VersionChange] Already fetching newer version 59261 > 59261
2016-09-29T21:26:40.307Z [FFC80B70 error 'Message' opID=SWI-1f3c266a] [MsgConnectionImpl::FinishSSLConnect] Error N7Vmacore3Ssl18SSLVerifyExceptionE(SSL Exception: Verification parameters:
Everything ok from a non-Win10 machine??
I have tried using the converter tool and it gets to 98% and fails. The best way to explain this is with a picture. There is a Windows 2008 R2 guest residing on a virtual disk that is 1.91 TB and the amount of data on this server is about 150 GB. I simply want to reduce the size of the virtual disk to something closer to 500 GB. There is a 1.4 TB unused partition in the Windows guest OS. The C and D volumes are both on the same VD. There has got to be a way to reduce the size of this thing and do away with this huge unused partition. I have Veeam Backup and Replication 8 at my disposal, the VMware converter tool standalone, diskpart, and other command-line Linux tools - it's ESXi 5.5. I would be super thankful if someone can give me some suggestions on how to do this. Seems like I tried restoring a backup and it restores it the same way with the unneeded partition. Tried the converter tool, that seems like the best way to accomplish this but I was doing something wrong. Please see attached... many thanks!
Sam Bob
thanks for reply
I have try to reboot my server
but it doesn't work
Hi Fluxblocker,
You can basically do it correctly with the vCenter Converter. After you select the part of the Destination Location you will go to the Options now, in there you can basically select which disk you can only migrate together with your virtual machine on the basic settings or you can also go for the Advance settings where you can actually select the capacity of the disk you want only to migrate.
Hope I was able to help.
Cheers.
Try any of the solutions below if some of it works. Make sure VMware tools is Installed or recently just Installed. if not you may reinstall your VMware tools once again before performaing any of the steps below.
1. If your host computer's screen resolution is high enough, you can enlarge the window, choose Fit Guest to Window to deselect it, then choose Fit Guest to Window once more to select it again.
2. If your host computer's screen resolution does not allow you to enlarge the window enough, do not use Fit Guest to Window. If it is selected, choose it again to deselect it. Then set the guest operating system's screen resolution to 640 x 480 or larger.
3. Inside of the directory where your guest operating system is stored, there is a file with a name like guestOS.vmx. While your virtual machine is not running, open your text editor (wordpad or notepad) and configure the (svga.maxWidth = "your number") and (svga.maxHeight = "your number") and start again your virtual machine.
4. In the VSphere client click the edit the settings of the Virtual Machine. Then select the Video card and specify the custom settings and possible to enable 3D Support.
Please let us know which of this works.
Cheers
ESXi 5.1.0
SUN FIRE X4170
Yesterday my ESXi host went down again but there's no log indicating it is powering down or reboot
There are only messages of powering up, only once a few days ago it was powered off.
~ # date
Fri Sep 30 02:58:28 UTC 2016
~ # grep -i power /var/log/vmksummary.log
2016-08-24T21:04:51Z bootstop: Host is powering off
~ # grep -i boot /var/log/vmksummary.log
2016-08-24T18:00:44Z bootstop: Host has booted
2016-08-24T21:04:51Z bootstop: Host is powering off
2016-08-24T21:53:21Z bootstop: Host has booted
2016-08-24T22:24:30Z bootstop: Host has booted
2016-09-20T08:24:39Z bootstop: Host has booted
2016-09-26T07:30:56Z bootstop: Host has booted
2016-09-26T10:59:54Z bootstop: Host has booted
2016-09-27T10:29:36Z bootstop: Host has booted
2016-09-30T02:00:32Z bootstop: Host has booted
~ # grep -i halt /var/log/vmksummary.log
~ # grep -i kernel /var/log/vmksummary.log
~ # esxcfg-advcfg -g /Misc/BlueScreenTimeout
Value of BlueScreenTimeout is 0
~ # grep -i fail /var/log/vmkernel.log | grep "2016-09-30"
ACPI Error (psparse-0621): Method parse/execution failed [\_SB_._OSC] (Node 0x410006676220)2016-09-30T01:59:35.972Z cpu3:4469), AE_AML_BUFFER_LIMIT
2016-09-30T01:59:35.972Z cpu3:4469)VMKAcpi: 161: Failed to evaluate _OSC: AE_AML_BUFFER_LIMIT
2016-09-30T01:59:39.759Z cpu2:4537)VMK_PCI: 1228: device 00:00:01.0 failed to allocate 1 vectors (intrType 1)
2016-09-30T01:59:39.759Z cpu2:4537)VMK_PCI: 1228: device 00:00:02.0 failed to allocate 1 vectors (intrType 1)
2016-09-30T01:59:39.759Z cpu2:4537)VMK_PCI: 1228: device 00:00:03.0 failed to allocate 1 vectors (intrType 1)
2016-09-30T01:59:39.759Z cpu2:4537)VMK_PCI: 1228: device 00:00:07.0 failed to allocate 1 vectors (intrType 1)
2016-09-30T01:59:39.759Z cpu2:4537)VMK_PCI: 1228: device 00:00:09.0 failed to allocate 1 vectors (intrType 1)
2016-09-30T01:59:39.759Z cpu2:4537)VMK_PCI: 1228: device 00:00:13.0 failed to allocate 1 vectors (intrType 1)
2016-09-30T01:59:39.759Z cpu2:4537)VMK_PCI: 1228: device 00:00:1e.0 failed to allocate 1 vectors (intrType 1)
2016-09-30T01:59:39.759Z cpu2:4537)VMK_PCI: 1228: device 00:00:1f.0 failed to allocate 1 vectors (intrType 1)
2016-09-30T01:59:39.759Z cpu2:4537)VMK_PCI: 1228: device 00:00:1f.3 failed to allocate 1 vectors (intrType 1)
2016-09-30T01:59:40.353Z cpu0:4469)WARNING: Team.etherswitch: TeamES_Activate:309:Failed to initialize beaconing on portset 'pps': Not implemented.
2016-09-30T01:59:43.565Z cpu5:4585)ScsiNpiv: 1525: GetInfo for adapter vmhba32, [0x41000c0cac80], max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, rv=-1, sts=bad0020
2016-09-30T01:59:44.567Z cpu4:4587)ScsiScan: 1016: Path 'vmhba32:C0:T0:L0' : No standard UID: Failure. ANSI version 'SCSI-2' (0x2).
2016-09-30T01:59:47.619Z cpu1:4593)ScsiNpiv: 1525: GetInfo for adapter vmhba0, [0x41000c0ccf40], max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, rv=-1, sts=bad0020
2016-09-30T01:59:47.619Z cpu1:4593)ScsiNpiv: 1525: GetInfo for adapter vmhba33, [0x41000c0cd540], max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, rv=-1, sts=bad0020
2016-09-30T01:59:47.619Z cpu1:4593)ScsiNpiv: 1525: GetInfo for adapter vmhba34, [0x41000c0cdb40], max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, rv=-1, sts=bad0020
2016-09-30T01:59:47.619Z cpu1:4593)ScsiNpiv: 1525: GetInfo for adapter vmhba35, [0x41000c0ce140], max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, rv=-1, sts=bad0020
2016-09-30T01:59:47.619Z cpu1:4593)ScsiNpiv: 1525: GetInfo for adapter vmhba36, [0x41000c0ce740], max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, rv=-1, sts=bad0020
2016-09-30T01:59:47.619Z cpu1:4593)ScsiNpiv: 1525: GetInfo for adapter vmhba37, [0x41000c0ced40], max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, rv=-1, sts=bad0020
2016-09-30T01:59:47.878Z cpu4:4600)ScsiScan: 1016: Path 'vmhba1:C0:T0:L0' : No standard UID: Failure. ANSI version 'SCSI-2' (0x2).
2016-09-30T01:59:47.886Z cpu4:4600)WARNING: ScsiScan: 1276: Failed to add path vmhba1:C1:T0:L0 : Not found
2016-09-30T01:59:47.887Z cpu4:4600)WARNING: ScsiScan: 1276: Failed to add path vmhba1:C1:T1:L0 : Not found
2016-09-30T01:59:47.986Z cpu4:4600)ScsiScan: 1016: Path 'vmhba1:C3:T0:L0' : No standard UID: Failure. ANSI version 'SCSI-3 SPC3' (0x5).
2016-09-30T01:59:48.079Z cpu4:4600)ScsiScan: 1016: Path 'vmhba1:C3:T1:L0' : No standard UID: Failure. ANSI version 'SCSI-3 SPC3' (0x5).
2016-09-30T01:59:48.127Z cpu4:4600)ScsiNpiv: 1525: GetInfo for adapter vmhba1, [0x41000c0cf340], max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, rv=-1, sts=bad0020
2016-09-30T01:59:53.419Z cpu7:4602)ScsiNpiv: 1525: GetInfo for adapter vmhba2, [0x41000c404ac0], max_vports=0, vports_inuse=0, linktype=0, state=1, failreason=0, rv=0, sts=0
2016-09-30T01:59:53.419Z cpu7:4602)ScsiNpiv: 1525: GetInfo for adapter vmhba3, [0x41000c0d0080], max_vports=0, vports_inuse=0, linktype=0, state=0, failreason=0, rv=-2, sts=bad0020
2016-09-30T02:00:01.657Z cpu0:4469)ScsiDeviceIO: 7065: Get VPD 80 Inquiry for device "mpx.vmhba1:C0:T0:L0" from Plugin "NMP" failed. Not supported
2016-09-30T02:00:01.657Z cpu0:4469)ScsiDeviceIO: 7075: Get VPD 83 Inquiry for device "mpx.vmhba1:C0:T0:L0" from Plugin "NMP" failed. Not supported
2016-09-30T02:00:01.657Z cpu7:4469)ScsiDeviceIO: 5880: Could not detect setting of QErr for device mpx.vmhba1:C0:T0:L0. Error Failure.
2016-09-30T02:00:01.805Z cpu7:4469)ScsiDeviceIO: 7065: Get VPD 80 Inquiry for device "mpx.vmhba1:C3:T0:L0" from Plugin "NMP" failed. Not supported
2016-09-30T02:00:01.805Z cpu7:4469)ScsiDeviceIO: 7075: Get VPD 83 Inquiry for device "mpx.vmhba1:C3:T0:L0" from Plugin "NMP" failed. Not supported
2016-09-30T02:00:01.926Z cpu7:4469)ScsiDeviceIO: 7065: Get VPD 80 Inquiry for device "mpx.vmhba1:C3:T1:L0" from Plugin "NMP" failed. Not supported
2016-09-30T02:00:01.926Z cpu7:4469)ScsiDeviceIO: 7075: Get VPD 83 Inquiry for device "mpx.vmhba1:C3:T1:L0" from Plugin "NMP" failed. Not supported
2016-09-30T02:00:03.147Z cpu0:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.600a0b800051249c000004204b599146. Error Failure.
2016-09-30T02:00:03.153Z cpu0:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.600a0b80003ac78400007b3b54aca949. Error Failure.
2016-09-30T02:00:03.160Z cpu0:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.600a0b80003ac6fe0000786b54aca240. Error Failure.
2016-09-30T02:00:03.191Z cpu3:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.600a0b80003ac6fe00007771548136d2. Error Failure.
2016-09-30T02:00:03.199Z cpu3:4469)ScsiDeviceIO: 7065: Get VPD 80 Inquiry for device "mpx.vmhba32:C0:T0:L0" from Plugin "NMP" failed. Not supported
2016-09-30T02:00:03.199Z cpu3:4469)ScsiDeviceIO: 7075: Get VPD 83 Inquiry for device "mpx.vmhba32:C0:T0:L0" from Plugin "NMP" failed. Not supported
2016-09-30T02:00:03.210Z cpu3:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.600a0b8000511fe600001df253fbca51. Error Failure.
2016-09-30T02:00:03.221Z cpu3:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.600a0b800051249c00001ec053fbc9b2. Error Failure.
2016-09-30T02:00:10.458Z cpu5:4823)WARNING: ScsiScan: 1276: Failed to add path vmhba1:C1:T0:L0 : Not found
2016-09-30T02:00:10.460Z cpu5:4823)WARNING: ScsiScan: 1276: Failed to add path vmhba1:C1:T1:L0 : Not found
2016-09-30T02:00:20.957Z cpu3:4099)NMP: nmp_ThrottleLogForDevice:2346: Cmd 0x85 (0x412400802b00, 5256) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2016-09-30T02:00:20.957Z cpu3:4099)ScsiDeviceIO: 2342: Cmd(0x412400802b00) 0x85, CmdSN 0x0 from world 5256 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2016-09-30T02:00:20.957Z cpu3:4099)NMP: nmp_ThrottleLogForDevice:2346: Cmd 0x4d (0x412400802b00, 5256) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2016-09-30T02:00:20.957Z cpu3:4099)ScsiDeviceIO: 2358: Cmd(0x412400802b00) 0x4d, CmdSN 0x1 from world 5256 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2016-09-30T02:04:27.398Z cpu0:4104)NMP: nmp_ThrottleLogForDevice:2346: Cmd 0x1a (0x4124007e3a40, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2016-09-30T02:04:27.398Z cpu0:4104)ScsiDeviceIO: 2342: Cmd(0x4124007e3a40) 0x1a, CmdSN 0x82c from world 0 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2016-09-30T02:30:20.664Z cpu6:4670)NMP: nmp_ThrottleLogForDevice:2346: Cmd 0x85 (0x4124007e6840, 5256) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2016-09-30T02:30:20.664Z cpu6:4670)ScsiDeviceIO: 2358: Cmd(0x4124007e6840) 0x4d, CmdSN 0x4 from world 5256 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2016-09-30T02:34:27.438Z cpu0:4603)NMP: nmp_ThrottleLogForDevice:2346: Cmd 0x1a (0x4124007cd0c0, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2016-09-30T02:54:27.458Z cpu5:4101)ScsiDeviceIO: 2342: Cmd(0x4124007abbc0) 0x1a, CmdSN 0x9a6 from world 0 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2016-09-30T03:00:20.724Z cpu7:4103)NMP: nmp_ThrottleLogForDevice:2346: Cmd 0x85 (0x4124007f0900, 5256) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2016-09-30T03:00:20.725Z cpu7:4103)ScsiDeviceIO: 2358: Cmd(0x4124007f0900) 0x4d, CmdSN 0x7 from world 5256 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2016-09-30T03:09:27.471Z cpu0:4104)NMP: nmp_ThrottleLogForDevice:2346: Cmd 0x1a (0x41240078bbc0, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
~ # grep -i error /var/log/vmkernel.log | grep "2016-09-30"
ACPI Error (dsopcode-0718): Field [CDW3] at 96 exceeds Buffer [NULL] size 64 (bits)2016-09-30T01:59:35.972Z cpu3:4469) [20080926]
ACPI Error (psparse-0621): Method parse/execution failed [\_SB_._OSC] (Node 0x410006676220)2016-09-30T01:59:35.972Z cpu3:4469), AE_AML_BUFFER_LIMIT
2016-09-30T02:00:01.657Z cpu7:4469)ScsiDeviceIO: 5880: Could not detect setting of QErr for device mpx.vmhba1:C0:T0:L0. Error Failure.
2016-09-30T02:00:01.813Z cpu4:4100)WARNING: LinScsi: SCSILinuxProcessCompletions:772:Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = AAC, Requested length = 16, Resid = -16
2016-09-30T02:00:01.813Z cpu7:4469)ScsiDeviceIO: 5880: Could not detect setting of QErr for device mpx.vmhba1:C3:T0:L0. Error Not supported.
2016-09-30T02:00:01.935Z cpu4:4100)WARNING: LinScsi: SCSILinuxProcessCompletions:772:Error BytesXferred > Requested Length Marking transfer length as 0 - vmhba = vmhba1, Driver Name = AAC, Requested length = 16, Resid = -16
2016-09-30T02:00:01.935Z cpu7:4469)ScsiDeviceIO: 5880: Could not detect setting of QErr for device mpx.vmhba1:C3:T1:L0. Error Not supported.
2016-09-30T02:00:01.936Z cpu2:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.6005076300808109400000000000000d. Error Not supported.
2016-09-30T02:00:02.595Z cpu6:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.6005076300808109400000000000000c. Error Not supported.
2016-09-30T02:00:02.604Z cpu0:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.6005076300808109400000000000000b. Error Not supported.
2016-09-30T02:00:02.616Z cpu0:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.60050763008081094000000000000009. Error Not supported.
2016-09-30T02:00:03.132Z cpu0:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.6005076300808109400000000000000a. Error Not supported.
2016-09-30T02:00:03.147Z cpu0:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.600a0b800051249c000004204b599146. Error Failure.
2016-09-30T02:00:03.153Z cpu0:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.600a0b80003ac78400007b3b54aca949. Error Failure.
2016-09-30T02:00:03.160Z cpu0:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.600a0b80003ac6fe0000786b54aca240. Error Failure.
2016-09-30T02:00:03.191Z cpu3:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.600a0b80003ac6fe00007771548136d2. Error Failure.
2016-09-30T02:00:03.199Z cpu3:4469)ScsiDeviceIO: 5880: Could not detect setting of QErr for device mpx.vmhba32:C0:T0:L0. Error Medium not found.
2016-09-30T02:00:03.210Z cpu3:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.600a0b8000511fe600001df253fbca51. Error Failure.
2016-09-30T02:00:03.221Z cpu3:4469)ScsiDeviceIO: 6394: Could not detect setting of sitpua for device naa.600a0b800051249c00001ec053fbc9b2. Error Failure.
Hi Brucehuai
This seems to be a hardware problem. You may try the steps below.
1. Try to reseat the power supply one by one and then reset the counters.
2. You may try to file for a support ticket to your direct vendor to check for the problem.
Hi Hdinh,
You may follow these two steps below.
A. In order to override the default DRS cluster settings for a Virtual Machine, you need to do the following.
B. You may create a group for your Virtual Machines on which host it must only run and not on the DRS Settings
1. Create a new DRS Group for Host
2. Create a new DRS Group for your Virtual Machines
3. Create a new DRS Rules to match with the Host with the Virtual Machines (Must run on host in group or Must not run on host in group)
Please let me know if any of it works.
Cheers.
Is there anything in hostd.log for the time it was shutting down?
Increase the Video memory size to 8 MB or more from VM edit settings and then try to set resolution in VM guest OS and console view options.
-
Haridas Vhadade
The best option is using a snapshot you've saved earlier. Virtual machine provides you a feature for saving snapshot, so that you can recover data if any problem or issue takes place. If there's nothing like that, you must try VMDK Recovery software to recover files from VMDK. The blog post shared below contains a very useful information regarding this. You must read the blog post.
VMDK Recovery Software Helps You Recover Files From VMDK | N. Sem's Blog
I hope this would be helpful here.
Regards.