Bug#891979: linux-image-4.9.0-6-amd64: Cannot use Windows 2016 Hyper-V in a KVM guest

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

Bug#891979: linux-image-4.9.0-6-amd64: Cannot use Windows 2016 Hyper-V in a KVM guest

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 escribió: On 03/03/2018 10:59 AM,

Bug#891979: linux-image-4.9.0-6-amd64: Cannot use Windows 2016 Hyper-V in a KVM guest

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

Bug#891979: linux-image-4.9.0-6-amd64: Cannot use Windows 2016 Hyper-V in a KVM guest

Package: src:linux Version: 4.9.82-1+deb9u3 Severity: normal Hi, 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