After updating three hosts out of five in a windows hyper-v cluster based on Nutanix using CAU tool, I noticed the Windows 7/2008 VMs stopped running on the updated hosts. Using the failover cluster manager, I managed to failover the VM to the non-updated host and it started working.
During troubleshooting, I came across the below two blogs which set me thinking:
Normal
0
false
false
false
EN-IN
X-NONE
AR-SA
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:”Table Normal”;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:””;
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:”Calibri”,sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-fareast-language:EN-US;}
In the Hyper-V manager, I noticed the Windows 2012 VMs were running without any issue but the Windows 7/2008 VMs were shown with the message “Cannot connect to Virtual Machine storage”. I was able to access the storage from the hosts without any problem and confirmed this with Nutanix support.
The Hyper-V hosts create symbolic links to the XML files of the VMs hosted in “C:\Programdata\Microsoft\Windows\Hyper-V\Virtual Machines”. The IDs did not match.
I deleted the Symbolic links in the Hyper-V host and then failed over the same VMs using the Failover Cluster Manager to the updated host from the non-updated host and the VMs started to work.
Powering The Shell 
Leave a comment