Hi again,
Yes, it definitely works fine with 4.14 from backports.
So, is it possible to have the fixes on the stretch kernel or do I
have to stick with the kernel from backports?
Also, does the backports kernel receive the security updates in a
timely fashion (i.e. at the same time as the stable kernel)?
Regards,
Antonio Huete
Antonio Huete Jiménez <tuxi...@quantumachine.net> escribió:
Hi,
My idea was to use stable as much as possible and use backports only
if the fixes were not going to be integrated on stable.
In any case since let me first make sure it works with 4.14.
Regards,
Antonio Huete
Raymond Burkholder <r...@oneunified.net> escribió:
On 03/03/2018 10:59 AM, Antonio Huete Jimenez wrote:
Package: src:linux
Version: 4.9.82-1+deb9u3
Severity: normal
On the latest linux-image, as shown in the details of this bug
report, and after enabling KVM nested it is possible to enable
Hyper-V role in Windows 2016 standard.
However the requirements are not met due to certain cpu features
not being correctly propagated.
This was reported more than one year ago upstream in Linux (see
https://bugzilla.kernel.org/show_bug.cgi?id=106621) and the fixes
are available from 4.10 onwards. As it \
happens, Debian Stretch is using 4.9 and after installing linux
source with debian patches I can't see the changes required.
Maybe try stretch-backports which currently has kernel 4.14.13?
https://packages.debian.org/stretch-backports/linux-image-4.14.0-0.bpo.3-amd64
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.