Are you using Libvirt? If so, you can just remove xsaves in the Libvirt XML ("<feature policy='disable' name='xsaves'/>">).
It seems to me that this is a Hyper-V bug, but I understand that this is not a configuration that happens on real hardware.
Adding the flag to all Skylake and newer systems (including Denverton and Snowridge) is the best choice, but we cannot just add it; if you want to send a patch, see the "Intel Atom Processor (SnowRidge)" model for an example of how to do it.
Are you using Libvirt? If so, you can just remove xsaves in the Libvirt XML ("<feature policy='disable' name='xsaves'/>">).
It seems to me that this is a Hyper-V bug, but I understand that this is not a configuration that happens on real hardware.
Adding the flag to all Skylake and newer systems (including Denverton and Snowridge) is the best choice, but we cannot just add it; if you want to send a patch, see the "Intel Atom Processor (SnowRidge)" model for an example of how to do it.