Quick Migration Revisited

Earlier today I participated in a webinar with VMware in which the subject of Microsoft’s Quick Migration functionality came up. I’ve discussed Quick Migration vs. live migration (VMotion in the VMware world) before, but this time I had the opportunity to see an interesting video demo of Quick Migration.

The video demo of Quick Migration is available here.

Now, I’ll grant you that this video was produced by VMware and will quite naturally be slanted against Microsoft in favor of VMware. With that in mind, let me ask this question: Could the problems shown in the demo be eliminated with a correct setup?

Microsoft experts and experienced Hyper-V testers/users, I’d love to hear your thoughts and feedback in the comments below. We all know that it’s possible to create a demo environment that doesn’t follow vendor best practices and therefore puts that vendor in a bad light; was this the case here? Or are these problems with Quick Migration accurate?

Tags: , , ,


  1. stu’s avatar

    As far as I can tell, this is exactly how the Quick migration service is sold – it’s a pause in service while the migration takes place. If the application you’re running can’t deal with a pause in service (i.e. the server disppearing for that time) then it will fail. The demo shows exactly expected behaviour. All that really means is that you have to plan for your migrations to take place.

  2. JoseRuelas’s avatar

    the only way I can see that could avoid this type of behaviour is that Microsoft needs to add something like VMotion.

    What do you think?

Comments are now closed.