Re:Degraded performance after forced reboot due to AWS insta...
by soccerdave on Wednesday January 03, 2018 @04:49PM
(#16065542)
So this sounds like this Intel bug will not impact performance on HVM instances.
[ Parent
| on HN ]
Re:Degraded performance after forced reboot due to AWS insta...
by panarky on Wednesday January 03, 2018 @05:26PM
(#16065907)
That's not what it says.
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.
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.
Re:Degraded performance after forced reboot due to AWS insta...
by drvdevd on Wednesday January 03, 2018 @05:17PM
(#16065806)
I don’t know enough about Xen to be sure, but I know typically your dom0 is a Linux kernel even (or especially) with HVM. If it’s been patched and is performing any paging on behalf of the guest, this will indeed affect performance of both paravirt and HVM instances.