Sometimes you wished you hadn’t invested all of your 50.000 dollars on an employee who will be doing “migrations” for you. So what am I talking about? Well imagine yourself in a 24×7 environment, or anyother environment for that matter and you just received an email about this patch. Yeah this patch NEEDS to be applied a.s.a.p. cause it’s a major vulnerability. So in other words, patch your Hyper-V. This means either a quick migration or shutdown the vm’s in any environment that would cause downtime either way. I think your $ 50.000(which probably isn’t the correct amount anyway) is well spend within matter of days.
Thanks for making our arguments valid.
By the way, make sure to patch your systems asap cause a new worm virus can be expected that takes advantage of this feature(;)) soon…
Andrew Storrs says
Nice one Duncan. 🙂
It effects Hyper-V (well Server Core) and requires a reboot – like you said “thanks for making our arguments valid.” I’ll be using this as another reason not to use Hyper-V when speaking with clients (and it’s a damn fine example of one at that!).
Sven Huisman says
It doesn’t matter if you’re running Hyper-V. The VM’s running Windows also needs this patch and those VM’s will need a reboot anyway…
Like VMware doesn’t make mistakes (remember August 12?).
But I get your point. VMotion still is a great and must have feature.
Duncan says
Everybody makes mistakes. And where people code their will always be bugs. Your vm’s will need to reboot anyway indeed, but I’d rather reboot then switch them off completely or do a quick migration and have a second down time.
This is not about your average bug, but about attacking the surface of your infrastructure environment.
Jason Boche says
Hyper-V lack of hot migration has been beat to death, however, it never becomes any less relevant.
Sven Huisman says
I can’t imagine a company (besides microsoft) using hyper-v in production anyway, even if it had live migration.