On Tue, Jan 09, 2018 at 04:02:34PM -0800, Anthony Liguori wrote:
> From: Anthony Liguori
>
> CVE-2017-5754 is problematic for paravirtualized x86 domUs because it
> appears to be very difficult to isolate the hypervisor's page tables
> from PV domUs while maintaining ABI compatibility. Instead o
On 01/09/2018 09:07 PM, Anthony Liguori wrote:
> On Tue, Jan 9, 2018 at 8:46 PM, Sarah Newman wrote:
>> vixen-upstream-v2 hangs for us after dumping the e820 map. We're able to
>> build and run vixen-upstream-v1.
>
> Can give me more details about your guest config? I'm happy to take a
> look a
On Tue, Jan 9, 2018 at 8:46 PM, Sarah Newman wrote:
> vixen-upstream-v2 hangs for us after dumping the e820 map. We're able to
> build and run vixen-upstream-v1.
Can give me more details about your guest config? I'm happy to take a
look and debug.
> My company needs serial input. It looks like
vixen-upstream-v2 hangs for us after dumping the e820 map. We're able to build
and run vixen-upstream-v1.
My company needs serial input. It looks like that wasn't implemented. If so,
and nobody else is working on patches to enable serial input, I believe
we can come up with something in the next
From: Anthony Liguori
CVE-2017-5754 is problematic for paravirtualized x86 domUs because it
appears to be very difficult to isolate the hypervisor's page tables
from PV domUs while maintaining ABI compatibility. Instead of trying
to make a KPTI-like approach work for Xen PV, it seems reasonable
