Re:Degraded performance after forced reboot due to AWS insta...
by jamesjoethomas on Thursday January 04, 2018 @01:02AM
(#16068373)
I don't think that's right, Ctrl-F for "HVM" here: https://xenbits.xen.org/xsa/advisory-254.html
In the HVM case an attacker can't generate hypervisor addresses because the hypervisor runs in a separate address space, so HVM isn't vulnerable to the most easily exploitable of the disclosed issues.
Amazon suggests moving to higher-performance instances to offset offset the performance hit from the fix.
HVM and m3 instances have higher performance for the same price, but they may also have been degraded by the fix.