dekoshal's Accepted Solutions

Consider using vSphere Replication for a single VM Replication. As, single VM only can not be replicated using array based replication assuming that there are multiple VM's  in that LUN. VMware Knowledge Base If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points. Best Regards, Deepak Koshal CNE|CLA|CWMA|VCP4|VCP5|CCAH https://hackhands.com/dkoshal/

Have a look on . labs.hol.vmware.com If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points. Best Regards, Deepak Koshal CNE|CLA|CWMA|VCP4|VCP5|CCAH

So i check the log file again and found another entry 2017-10-03T21:30:49.147Z| vmx| I120: Tools: sending 'OS_Halt' (state = 1) state change request 2017-10-03T21:30:49.147Z| vmx| I120: Vix: [3006474 vmxCommands.c:534]: VMAutomation_InitiatePowerOff. Tried to soft halt. Success = 1 as per the vmware kb#1019064 this means A user or API initiated request to shutdown a virtual machine. If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points. Best Regards, Deepak Koshal CNE|CLA|CWMA|VCP4|VCP5|CCAH

Is this is what you are looking for. https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/product-lifecycle-matrix.pdf If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points. Best Regards, Deepak Koshal CNE|CLA|CWMA|VCP4|VCP5|CCAH

Processor "Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz" Backtrace 2017-07-22T00:07:38.309Z cpu17:38249)@BlueScreen: #GP Exception 13 in world 38249:vmast.38248 @ 0x418028088d64 2017-07-22T00:07:38.309Z cpu17:38249)Code start: 0x418028000000 VMK uptime: 37:14:18:23.572 2017-07-22T00:07:38.310Z cpu17:38249)0x4391ab49baf0:[0x418028088d64]TimerRecomputeInterrupt@vmkernel#nover+0xf4 stack: 0x4391ab4a7000 2017-07-22T00:07:38.310Z cpu17:38249)0x4391ab49bb20:[0x41802808b49f]Timer_Interrupt@vmkernel#nover+0x117 stack: 0xef 2017-07-22T00:07:38.311Z cpu17:38249)0x4391ab49bb50:[0x41802805a652]IntrCookie_DoInterrupt@vmkernel#nover+0x27a stack: 0x7780 2017-07-22T00:07:38.311Z cpu17:38249)0x4391ab49bc00:[0x418028056d60]IDT_IntrHandler@vmkernel#nover+0x104 stack: 0x0 2017-07-22T00:07:38.311Z cpu17:38249)0x4391ab49bc30:[0x4180280c8044]gate_entry_@vmkernel#nover+0x0 stack: 0x0 2017-07-22T00:07:38.312Z cpu17:38249)0x4391ab49bcf0:[0x41802830515a]Power_HaltPCPU@vmkernel#nover+0x1ee stack: 0x417fe8283f20 2017-07-22T00:07:38.312Z cpu17:38249)0x4391ab49bd40:[0x418028212078]CpuSchedIdleLoopInt@vmkernel#nover+0x2f8 stack: 0x1ba1f9a2d4e578 2017-07-22T00:07:38.313Z cpu17:38249)0x4391ab49bdc0:[0x4180282157d3]CpuSchedDispatch@vmkernel#nover+0x16b3 stack: 0x2054c7 2017-07-22T00:07:38.313Z cpu17:38249)0x4391ab49bee0:[0x418028216398]CpuSchedWait@vmkernel#nover+0x240 stack: 0x0 2017-07-22T00:07:38.313Z cpu17:38249)0x4391ab49bf60:[0x418028093c10]VmAssistantProcessTasks@vmkernel#nover+0x1bc stack: 2017-07-22T00:07:38.307Z cpu17:38249) [45m [33;1mVMware ESXi 6.0.0 [Releasebuild-5572656 x86_64] [0m Each VM is having multiple worlds that can be seen in the esxtop. vmast: This world is used for memory scanning.  This can be identified by the GID which will be common for all the worlds for the give Virtual machine Understanding Exception 13 and Exception 14 purple diagnostic screen events in ESX 3.x/4.x and ESXi 3.x/4.x/5.x/6.x (102… A general protection fault (Exception 13) occurs under one of these circumstances: 1.The page being requested does not belong to the program requesting it (and is not mapped in program memory) 2.The program does not have rights to perform a read or write operation on the page The Exception 13 General Protection Fault may be caused by either a hardware or a software issue. Further looking ESXi host fails with PSOD when using Intel Xeon Processor E5 v4, E7 v4, and D-1500 families (2146388) | VMware KB Look into additional info. similar backtrace is visible. Reported issue can occur when running a supported version of ESXi host with Intel Xeon Processor E5 v4, E7 v4, and D-1500 families, you may experience these symptoms. Looks like its a Hardware issue and need  system BIOS (firmware) upgrade. Check kb for more details. If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points. Best Regards, Deepak Koshal CNE|CLA|CWMA|VCP4|VCP5|CCAH

Why you want to do that when ESXi does it for you? The ESXi system has two independent banks of memory I.e /bootbank & /altbootbank, each of which stores a full system image, as a fail-safe for applying updates. When you upgrade the system, the new version is loaded into the inactive bank of memory, and the system is set to use the updated bank when it reboots. If boot fails, system boots from the previously active bootbank. Boot loader compares the boot.cfg in each bootbank Loads the newest (build=) and functioning (bootstate=0) bootbank If you found this or any other answer helpful, please consider the use of the Helpful to award points. Best Regards, Deepak Koshal CNE|CLA|CWMA|VCP4|VCP5|CCAH

With VMotion,  you can move Virtual machine from one ESX Server to another with no downtime for the users. For this datatsore(where virtual machine files are located) should be mounted on both source and destination esxi hosts Host Configuration for vMotion VMware vSphere 5.1 Storage VMotion is similar to VMotion it move the virtual machine files from one datastore to another without any downtime for the users. It can be helpful when you are moving vm from local datastore to a shared datastore. If you found this or any other answer helpful, please consider the use of the Helpful to award points. Best Regards, Deepak Koshal CNE|CLA|CWMA|VCP4|VCP5|CCAH