Re:Vixen: A PV-in-HVM shim
by aliguori on Monday January 08, 2018 @07:54PM
(#16102495)
We're still working the details out upstream but the TL;DR is that the way to address Meltdown with Xen PV is to use nested virtualization so that the outer guest is an HVM or PVH guest.
[ Parent
| on HN ]
Is this what AWS is doing?
Yes, all customer PV instances in EC2 are running in an HVM container and are protected against the guest-to-guest Meltdown vulnerability.
As with all virtual and physical machines, patches are necessary to protect against process-to-process Meltdown within the OS itself. Those are starting to roll out from the respective vendors although it will take time for those to work inside a PV instance.
Re:Vixen: A PV-in-HVM shim
by Vogtinator on Tuesday January 09, 2018 @03:02AM
(#16104388)
Doesn't this still allow to read memory from the hypervisor shared between the PV VMs in a HVM container?
The intention, from my understanding, is not to boot multiple PV guests inside of one HVM shim, but instead treat it as more of a packaged deal - for each PV guest, you will be running it inside an independent vixen shim. So 5 PV guests, 5 vixen shims, etc.
correct.
No, because page tables are isolated between guests.
From the post: "all PV instances in EC2 are
using this"