From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: VMX ideas Date: Wed, 29 Oct 2008 10:45:56 -0500 Message-ID: <49088534.60202@codemonkey.ws> References: <687FC948-DBF4-4A7C-AD14-F6DB53A092D6@suse.de> <49088310.2090702@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Graf , KVM list To: Gerd Hoffmann Return-path: Received: from mail-gx0-f31.google.com ([209.85.217.31]:57732 "EHLO mail-gx0-f31.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753367AbYJ2PqB (ORCPT ); Wed, 29 Oct 2008 11:46:01 -0400 Received: by gxk12 with SMTP id 12so151830gxk.13 for ; Wed, 29 Oct 2008 08:46:00 -0700 (PDT) In-Reply-To: <49088310.2090702@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Gerd Hoffmann wrote: > Alexander Graf wrote: > >> So I was thinking hard on what to do to circumvent this problem and came >> up with several approaches: >> > > >> 3. Create a root mode bloat framework >> > > 4. Enter vmx root mode when the first user opens /dev/kvm and leave it > when nobody uses it any more? > > Also note that there has been some discussion on lkml to move vmx-root > on/off out of the kvm module into the kernel. There are a few places > where it would be useful for the kernel to handle that without the kvm > module being involved, crashdump kexec for example. With that and some > locking in place (so only one can use vmx-root at a time) and > hypervisors being friendly to each other and grab vmx-root only when > they have a guest to run we should be set? > There was some patch that went into KVM that would indicate in CPU state that VT root mode was enabled so that VMware could detect that someone else was using VT. Look through the archives. Regards, Anthony Liguori > cheers, > Gerd > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >