lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 2 Oct 2017 11:18:16 +0100
From:   George Dunlap <dunlapg@...ch.edu>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     Lai Jiangshan <jiangshanlai+lkml@...il.com>,
        LKML <linux-kernel@...r.kernel.org>, kvm@...r.kernel.org,
        Juergen Gross <jgross@...e.com>, rusty@...tcorp.com.au,
        lguest@...ts.ozlabs.org,
        "the arch/x86 maintainers" <x86@...nel.org>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        xen-devel <xen-devel@...ts.xenproject.org>,
        Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [Xen-devel] KVM PV (was: Re: [PATCH v2 2/2] x86/lguest: remove
 lguest support)

On Fri, Sep 29, 2017 at 5:39 PM, Paolo Bonzini <pbonzini@...hat.com> wrote:
> On 29/09/2017 17:47, Lai Jiangshan wrote:
>> Hello, all
>>
>> An interesting (at least to me) thinking came up to me when I found
>> that the lguest was removed. But I don't have enough knowledge
>> to find out the answer nor energy to implement it in some time.
>>
>> Is it possible to implement kvm-pv which allows kvm to run on
>> the boxes without hardware virtualization support, so that
>> qemu/kvm can be used on clouds such as aws, azure?
>
> No, please don't. :)  Even Xen is moving from PV to PVH (paravirtualized
> hardware with event channels, grant tables and the like, but still using
> hardware extensions for MMU).

That said, the main pain point for Xen's PV so far has been the fact
that we expose the real pagetables directly to the guest, in order to
avoid having to do use shadow pagetables.  If you're willing to take
the performance hit and use an existing shadow pagetable
implementation from the start, it might not be so bad from a
development perspective.

Still, I'm betting it will be a lot more work than you expect. :-)

 -George

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ