- Kenon Owens, Microsoft
- Nate Lasnoski, MVP, Data Center
- Gene Ferioli, Microsoft (Appv team)
- Taylor Broan, Microsoft
- Robin Brandl, Microsoft
This is an open round table style discussion surrounding all of Microsoft's virtualization products.
Three reasons to switch from VMWare to Microsoft HyperV:
- Cost
- End-to-end Manageability
- something else … didn't really catch it … must not have been that important. :P
NIC Teaming
Taylor Broan (Microsoft) openly admitted that there is a gap with their product and VMware when it comes to NIC Teaming. They are working hard at fixing this. They mentioned that Microsoft NIC teaming works best with Intel NIC’s, but not so much with other vendors (*cough* broadcom *cough*).
Hyper-v wish list (from audience)
- Improved performance on snapshot-ing
- More integration with VMM
- Better memory support (this is coming real soon)
- Better monitoring
- Microsoft countered that this is there, you just need to know how to get it.
- Create virtual networks on all nodes of a cluster – or create a distributed virtual switch.
- Multiple virtual CPU’s
Client side hypervisor (VDI)
There was a large discussion between the audience and the VDI team on whether the hypervisor should run client side or not. Microsoft's stance was “it doesn't need to run client side until the industry demands it.” The audience was mixed on whether this was needed.
Server AppV
The lead program manager for AppV was in attendance and announced that they are developing a Server side AppV capability. He polled the audience if they would run apps and o/s’s 1:1 or 1:many. Most of the audience chose 1:1 – for simplicity of management. Helped him continue the product development path.
Overall this session made me feel vulnerable for switching to HyperV – I am glad we are “piloting” it this summer. Although the cost savings is very attractive, the quality of product and lack of feature set has me concerned. (Especially in the Linux side). Well see how the pilot goes.
No comments:
Post a Comment