hypnotoad wrote: » How to ruin your saturday night: 1. Bring up a new Hyper-V server using your Windows 2008 RTM disc. For some reason the Hyper-V update fails, so you are still running Beta Hyper-V (which was on RTM). You are unaware of this, because who really looks at all those updates anyway when bringing up a new server? 2. Move your existing VHD's to your new server. 3. Create new VM's using your existing VHD's and let them start up. Let them boot in the background while you get all your VM's going. 4. Say "WTF" as Hyper-V proceedes to corrupt all of the guest VHD's and totally ruin half your servers! 5. Spend all night restoring VHD's from backup. The lesson: never start a guest created in "Full" using the "Beta" host. It will corrupt the guest's VHD! Thanks, Microsoft.
JDMurray wrote: » It sounds like you've just written VMWare's next print ad!
Jordus wrote: » So because you declined to properly patch a new machine, you are going to try and save face by blaming Microsoft?
Jordus wrote: » So because you declined to properly patch a new machine, you are going to try and save face by blaming Microsoft? I think this simply should serve as a reminder to stick to best practices and do things by the book. (They are called "BEST" for a reason)
HeroPsycho wrote: » Honestly, and I like Microsoft, and defend them against a lot of criticism, but I do think including beta software on RTM media is asking for stuff like this to happen.
astorrs wrote: +1 Including the unreleased beta version of Hyper-V as an installable role with 2008 RTM was stupid. I understand why they wanted to do it, but it should have just sent you to a website to download it - which then could have been updated when Hyper-V RTM'd. Either that or you could just follow the best Hyper-V safety tip offered above... use VMware ESX.
bertieb wrote: » Still, this probably makes the guys at VMWare chuckle a bit.
bertieb wrote: » +1 to all this (Sorry, had to jump on the bandwagon here) Still, this probably makes the guys at VMWare chuckle a bit.
HeroPsycho wrote: Kinda like how Microsoft must have chuckled at the ESX 3.5 Update 3 licensing bug fiasco. Don't get me wrong, I like VMware virtualization products more than MS, but VMware ain't exactly perfect, either...
darkerosxx wrote: » Classic Microsoft, though, IMO, you shouldn't expect less.
HeroPsycho wrote: » I disagree. Microsoft is usually better about this kind of thing. You can site mistakes like this by any major IT company. I wouldn't say it's "classic Microsoft". I remember in my newb days upgrading an ESX server from 2.5 to 3, and it blowing up the VMFS volume on the local storage, and all the VM's were lost as an example. And in Microsoft's defense in this case, it was BETA software that has the problem. Like I said, my issue is it's easy to assume that all software included on install media for W2K8 should be production grade code.
darkerosxx wrote: » This is no one's fault but Microsoft's and their update should have allowed VM's created in beta to be used after the update. At they very least, it should say "UPGRADING FROM HYPER-V INCLUDED IN THE INSTALL MEDIA WILL BREAK YOUR VIRTUAL MACHINES!" and require approval before continuing.
darkerosxx wrote: » I installed the server and accepted usage of the beta Hyper-V, made my VM's, then updated several days later and this happened.
