Changes between Initial Version and Version 1 of Ticket #21687, comment 2

Ticket #21687, comment 2

initial	v1
1	1	Still not fixed in VirtualBox 7.0.12 -- does not work on Xeon w5-2455X (no VM can be started).
2	2
3		If a person who wrote the relevant XSAVE/XRESTORE code has read Intel CPUID manual they'd have known that you can't define X86FXSTATE as a compile-time constant, because future CPUs will report different ~~values. Sapphire Rapids reports 0x2B00 because of AMX instruction set extensions which are supported and enabled in Linux and Windows 11~~ (Windows 10 and older do not enable AMX).
	3	If a person who wrote the relevant XSAVE/XRESTORE code has read Intel CPUID manual they'd have known that you can't define X86FXSTATE as a compile-time constant, because future CPUs will report different state store sizes. Sapphire Rapids reports 0x2B00 because of AMX instruction set extensions which are supported and enabled in Linux and Windows 11 hosts (Windows 10 and older do not enable AMX).
4	4
5	5	I can't believe Sapphire Rapids support was not validated at launch, let alone six months later and counting.