News for hackers. Stuff that matters.
Re:Vixen: A PV-in-HVM shim by jlgaddis on Monday January 08, 2018 @08:01PM (#16102537)
Is this what AWS is doing?
Re:Vixen: A PV-in-HVM shim by aliguori on Monday January 08, 2018 @08:55PM (#16102836)
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?
Re:Vixen: A PV-in-HVM shim by cthalupa on Tuesday January 09, 2018 @04:59AM (#16104881)
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.
Re:Vixen: A PV-in-HVM shim by quanstro on Tuesday January 09, 2018 @06:02AM (#16105157)
correct.
Re:Vixen: A PV-in-HVM shim by bonzini on Tuesday January 09, 2018 @03:21AM (#16104455)
No, because page tables are isolated between guests.
Re:Vixen: A PV-in-HVM shim by jacobn on Monday January 08, 2018 @08:29PM (#16102696)
From the post: "all PV instances in EC2 are using this"
Re:Vixen: A PV-in-HVM shim by jlgaddis on Monday January 08, 2018 @08:43PM (#16102774)
Yeah, thanks, not sure HTF I missed that the first time.