Windows 2008 R2 Hyper-v Clustering: shutdown VM turns it into saved state and can't start/edit/delete


i have 2 node windows 2008 r2 hyper-v cluster(hypv1 , hypv2) both nodes hp proliant dl380 g7. csv volume1 on hp p2000 g3 fibre channel san. i'm having strange issue here: if volume1's owner hypv1 , create vm on hypv1, fine. same thing if volume1's owner hypv2 , create vm on hypv2 works fine.

problem when owner of volume1 hypv2 , create vm on hypv1, when shutdown or reboot vm, turns vm saved state , can't it, can't start/edit/delete. right after shutdown, in hyper-v manage says status of vm "off-critical, cannot access virtual machine configuration storage". after couple of minutes becomes saved state. in hypv1's system log warning message:

{delayed write failed} windows unable save data file \virtual machines\b4d2c89e-3df0-4aab-aa1d-3852411b8bc4.xml. data has been lost. error may caused failure of computer hardware or network connection. please try save file elsewhere.

if owner of volume1 hypv1 , create vm on hypv2, when shutdown vm becomes "off-critical, cannot access virtual machine configuration storage", after couple of minutes becomes "off" , can start or edit no problem. same warning message in hypv2's system log well.

i've done quite research didn't find any solution. hopefully someone here can me out problem. in advance. 

hi give update in case else run similar problem. nailed problem: caused ca arcserve backup open file agent on server. after removed agent normal way should be.

 

jason

 



Windows Server  >  High Availability (Clustering)



Comments

Popular posts from this blog

Edit Group Policy

Hyper-V VM not reaching OS 'Logon' screen

DNS question...