I’ve upgraded the first of our hosts in our Windows Server 2008 Hyper-V cluster to Service Pack 2. I wanted to move VM’s to this host so I could upgrade the next host to SP2. I opened VMM 2008 and attempted a migration of the first VM. I was offered a “zero star” score on the migration, i.e. VMM refused to do it. The reason given was:
So, VMM 2008 refuses to migrate a VM from a W2008 SP1 Hyper-V host to a W2008 SP2 Hyper-V host. That’s not good for upgrade scenarios. These are production VM’s so I can’t go about doing stops and restarts.
My workaround was simple. Bypass VMM and go straight into the Failover Clustering MMC. I connected to the cluster and migrated the resource for the VM’s in question. That worked perfectly.
So here’s my planned (at the moment) Hyper-V cluster Service Pack upgrade strategy:
- Apply the VMM 2008 rollup (see my recent posts) to the VMM server
- Migrate VM’s to leave a single host (host 1) with no VM’s.
- Upgrade host 1 to SP2
- Wait a day or two
- Use the Failover Cluster MMC to migrate VM’s from host 2 to host 1
- Upgrade host 2 to SP2
- Repeat steps 4 to 6 as required for additional hosts
It’s worked for me on two non-critical VM’s. I’m checking with MS if they’d be 100% happy with this. Until I hear back, I’m pausing things.
I too have experienced this migration issue. I have 3 hyper-v hosts and all have been upgraded to W2k8 Svc pk2, and the third host which I wanted to migrate a vm to is indicating the lower vmm version number.
I have attempted to install windows update KB967902 to the third host, this update looks like it would raise the vmm version number to the matching one, but the host server will not accept the update.
I don’t see why W2k8 would not have updated all hosts to the same vmms version number.
Does Microsoft acknowledge this issue, and is there a fix???
The solution I offered above was OK’d by some people I know in MS so that’s what I used. Make sure the IC’s are upgraded after the upgrade is completed.