Hurray, Hyper-V has been released. Yes, I’m sure every blogger and newsy person on the planet is posting something about Microsoft’s release today (as they should). But… how many of those posters have been testing Hyper-V since the fall of last year. :>)
Anyhow, as a general rule, I don’t talk about (beta and RC) products I’m currently testing. That way I don’t violate any NDAs. However, now that Hyper-V has been released to the masses the veil of non-communications can finally be removed.
This being said, I give the product team a glowing two thumbs up and a nice pat on the back. Hyper-V is the feature that makes Windows Server 2008 complete (you complete me). After all, Hyper-V can run on any 64-bit Windows Server 2008 machine (minus several “modern” requirements). Thus, I truly believe that VMWare’s hold on the market will come to be challenged once MS solves several items.
- Expands the number of guest OSes the client integration tools support (I’m going to suggest open source).
- RTMs Virtual Machine manager, please.
On another note:
I didn’t get a chance to post feedback about a problem I encountered to the Hyper-V team before RTM. The darn thing was already in escrow. Anyhow, before posting this in the forum, I figured I’d post the details here first. Basically, I’ve noticed an odd scenario with the following setup:
- Hyper-V Host.
- Windows Server 2008 Guest (Domain Controller that also hosts DHCP services).
Basically, when the DHCP server service is enabled you get the following behavior:
- The DC takes about 5 minutes to fully boot up.
- In certain cases (it’s random) the DC will boot up, run for about 10 minutes and then just drop off the network. When this occurs you need to reboot the machine.
- When you shutdown or reboot the DC, the machine will get into a state where the screen says shutting down. However, it will just sit there with CPU pegged at around 45%.
Needless to say, if you remove the DHCP server role or disable the DHCP server service everything goes back to normal. I also haven’t tried delaying the start of the DHCP server service. Additionally, I was testing RC version of Hyper-V and still need to verify the issue on the RTM version.
Anyhow… if you are having the same issue… please comment…
