I thought I would revisit this subject now that version 2.1 of the integration components has reached release candidate stage. You really will want to use v2.1 because it introduces SMP support for multiple vCPU’s (up to 4) in a Linux VM as well as clock synch and host power integration (for clean guest shutdown or state save).
My original discussion said that if you were doing enterprise Hyper-V then you are probably also running Operations Manager. The beauty of System Center and Hyper-V being used together is that you get a single management system for the entire computing stack.
OpsMgr 2007 R2, with Cumulative Update 1 supports a certain set of Linux distributions, versions and architectures. Hyper-V’s Linux Integration Services 2.1 supports another set. You really want to pick a Linux from the commonly supported distros. The below diagram should help with that.
Note that RHEL x64 does not support the Pluggable Time Service integration service. It also doesn’t have support from Project Satori (MS/Citrix project) for the VSC to capture a mouse.
It appears that SLES 11 (x86 and x64) and with RHEL 5 (x86 and x64) are the two to go with for deployment in the near future. You might steer clear of RHEL x64 (and choose RHEL x86) if the partial support exceptions are an issue.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.
No related posts.