MS has posted the top support issues PSS faced when dealing with Hyper-V. This was for the last quarter- what we in the normal world call Q1 2009 … what MS calls Q3 2009 (we’re in Q4 for them now).
As expected, some of the top issues are:
- People using the pre-RTM build that’s included on the W2008 media. That was a dumb move by MS. They should never have put pre-RTM code on there. This isn’t 20-20 hindsight either – it was obvious to everyone at the time that I talked to that this would lead to issues. At the very least, there should have been big screaming, red, flashing alarms declaring it to be pre-RTM.
- Lack of documentation. I’ve mentioned this over and over before. The TechNet library is incomplete. There’s plenty of us out there trying to fill in the gaps but we’re facing a moving playing field with mixed messages coming from PSS and the Hyper-V team.
- Virtualisation/DEP not enabled in the BIOS: This is possible to do with a Core installation for the parent OS. It’s also possible when the motherboard is replaced (as I discovered).
- Snapshots: Lots of issues there. My advice is simple: don’t use them in production.