Behind the scenes
While I do enjoy reading the comments - let me explain a bit of the behind the scenes stuff.
Letting people know that they have the *right* version of the integration components installed inside a virtual machine is quite important. First, it helps users avoid a number of common problems - second, it helps avoid a huge annoyance. That is the annoyance of hitting a problem, calling Microsoft support, and having them say "please update your integration components before we do anything else".
To this end - we have spent a chunk of time trying to make sure we detect when the wrong version of the integration components are present - and do as much as we can to indicate what is happening.
The problem is that all of our systems for doing this are built around the Windows integration components - which ship as part of the host operating system. This means that they are versioned along with the host operating system, and we can just check their versions against the host operating system version. This story is completely different for Linux. The Linux integration components ship as part of Linux. They have a completely different versioning and release system to the Windows integration components.
The unfortunate result is that you can have a Linux guest operating system that has the right components installed, with all the necessary functionality - but Hyper-V is confused about the support stance.
The primary reason why we published the document that is being referred to in this article is so that users would not be "given the run around" if they called up Microsoft support when running a Linux guest with the latest integration components.
Hopefully, this is something that we can handle better in the future.
Cheers,
Ben (Hyper-V Program Manager - A.K.A. Virtual PC Guy)