Has anybody heard about compatibility problems of VC2.0.1 with ESX 3.0.1 and ESX 3.0.2 in one cluster?
My cluster (5 x identical HP DL385G1 with ESX 3.0.1, patches from 31.01.2007) worked well with HA and DRS in VC2.0.1.
Two weeks ago I included a new host (HP DL585G2 with ESX 3.0.2) into this cluster. This host is not ready: VMotion is not active yet because I haven't added the CPU masks in the VMs.
Until now it also seemed to work well: DRS did not take notice for this new host (exept one little thing I posted in another thread).
But in the last two days I had a strange experience: suddenly I could not create new VMs (they queued and timed out, but last week it worked well) or migrate running VMs between my "old" hosts (they also timed out, but the migration seemed to be done).
New start of the VC server did not help. But after switching off DRS everything seemed to be okay again.
Has anybody similar experience? Is it a problem of ESX 3.0.1 and 3.0.2 in one cluster? Or is it because of the not VMotion ready new host?
Regards, Dietmar
