fourth node in Hyper-v cluster unable to create VHDs


hello, 

i have added fourth node our hyper-v failover cluster , unable live migrate or create new vms in scvmm 2008 r2 sp1, failover cluster manager or hyper-v manager.

the new node has identical nic , hardware configuration , difference sp1 others not.

i have:

  • installed dell san drivers (not management utils of kind) 
  • enable vt , dep in bios , power cycled
  • configured iscsi multipath san
  • added node host group (presenting luns)
  • added node cluster

i can confirm csvs readable , writeable new node, however, can't create new vm or live migrate existing 1 it. here details of each scenario:

creating new vm

in hyper-v manager, fails error "a virtual disk support provider specified file not found". , no changes made.

in scvmm, fails @ 82% after few seconds , gives more information:

 

error (12700)

vmm cannot complete hyper-v operation on the  <host> server because of error: 'the system failed create 'c:\clusterstorage\volume2\testagain\testagain_disk_1.vhd'. error code: virtual disk support provider specified file not found. 

 (a virtual disk support provider specified file not found (0xc03a0014)) 

recommended action

resolve issue in hyper-v , try operation again.

 

the folders vm created, bootable (in hyper-v manager), no disks present

live migrating vm

this fails @ 99%, assume @ point dirty blocks of memory trying moved, following error:

 

error (10698)

virtual machine <vm> not live migrated virtual machine host <host> using cluster configuration. 

 (unspecified error (0x80004005)) 

 

recommended action

check cluster configuration , try operation again.

performing same operation in failover cluster manager says migration failed.

 

here steps i've performed while troubleshooting:

  • changed relevant fsdepends dword 0
  • configured quorum disk in fcm
  • changed "network live migration" in fcm
  • evicted node cluster, pulled off , reconfigured iscsi stuff, , re-added cluster
  • services running on old , new hosts identical

i @ loss i've missed setting up, , appreciated

thanks

ben

 

hi ben,

after adding new node, did run "validate configuration" wizard entire solution?  did come clean?

does new node have same processor type , version?  if live migrating different version in same processor family, make sure have checked 'processor compatibility' option under process settings vm trying live migration.

thanks,
symon perriman
technical evangelist
microsoft



Windows Server  >  Hyper-V



Comments

Popular posts from this blog

List Styles

for loop and start-job from cmd.exe

The Windows Management Instrumentation (WMI) service cannot be started . Failed