We have a (2) node Hyper-V Failover Cluster created; first node (node1) is an HP DL385 G6 running Server 2008 R2 SP1 Data Center, the second node (node2) a new HP DL385 G7 also running Server 2008 R2 SP1 Data Center, both servers are using AMD Opteron CPUs but from different families. The cluster validation tests all passed, and the cluster is being managed via SCVMM 2012.
We ran into our original issue with node2, the HP DL385 G7, when it failed to start/run any VMs. This was resolved by applying Microsoft Hotfix 2568088 which fixed an issue with Hyper-v and AVX "Bulldozer" processor support. The current issue is trying to live migrate VMs to between nodes under certain circumstances. A VM can be deployed directly to or started on node2, it can then be live migrated between nodes without issue. Note: Processor compatibility feature has been enabled on all VMs. If the VM is started or deployed on node1 first, it cannot be live migrated to node2. SCVMM presents an error about Processor compatibility and fails to proceed. However the same VM in a stopped state can be migrated to node2 and started without issue. After that, live migrations to node1 and back to node2 will succeed. It's just when the VM starts on node1 that it cannot be live migrated to node2.
We are looking for solution or viable workaround until 2008 R2 SP2 is released and "hopefully" supports AVX.
- נערך על-ידי timbart יום חמישי 07 יוני 2012 15:51