From: Pavel Machek <pavel@xxxxxx> Sent: Wednesday, May 4, 2022 10:23 AM > > Hi! > > > Linux code for running as a Hyper-V guest includes special cases for the > > first released versions of Hyper-V: 2008 and 2008R2/Windows 7. These > > versions were very thinly used for running Linux guests when first > > released more than 12 years ago, and they are now out of support > > (except for extended security updates). As initial versions, they > > lack the performance features needed for effective production usage > > of Linux guests. In total, there's no need to continue to support > > the latest Linux kernels on these versions of Hyper-V. > > > > Simplify the code for running on Hyper-V by removing the special > > cases. This includes removing the negotiation of the VMbus protocol > > versions for 2008 and 2008R2, and the special case code based on > > those VMbus protocol versions. Changes are in the core VMbus code and > > several drivers for synthetic VMbus devices. > > > 2008 and 2008R2, so if the broader Linux kernel community surfaces > > a reason why this clean-up should not be done now, we can wait. > > But I think we want to eventually stop carrying around this extra > > baggage, and based on discussions with the Hyper-V team within > > Microsoft, we're already past the point that it has any value. > > Normal way to do such deprecations is to put printks in first, then hide it > under config option noone sets, and wait for year or so if anyone complains. > Are there any examples of doing these deprecation steps that you can point me to? I did not see anything in the Documentation directory covering the deprecation process you describe. I'd also make the case that we are already well down the deprecation path. For at least the last 5 years, the public Microsoft documentation for Linux guests has listed Hyper-V 2012 R2 as the earliest supported Hyper-V version. Other current and new Microsoft products aren't supported on Hyper-V 2008/Win7 either -- the usual Word/Excel/ PowerPoint, etc. fall into this category as well as Windows 10 and Windows 11 as guests. So for a rare user who might still be using Hyper-V 2008/Win7, there's no reasonable expectation of being able to run the latest upstream Linux kernel on Hyper-V 2008/Win7. Other current software doesn't. Given that running Linux guests on Hyper-V sort of implicitly combines Microsoft commercial thinking and Linux open source thinking about version support, I could see putting the old Hyper-V version support under a config option that defaults to "no", with a deprecation comment, and seeing if that garners any complaints. But given the broader situation with Hyper-V 2008/Win7, in my judgment even that is more cautious than we need to be. Michael > We can't really remove code that is in use. > > Best regards, > Pavel
