From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] Re: [PATCH] qemu-kvm: Switch to upstream -enable-kvm
 semantics
Date: Tue, 21 Dec 2010 10:56:50 -0600
Message-ID: <4D10DC52.9010301@codemonkey.ws>
References: <m3mxo7ox0v.fsf@blackfin.pond.sub.org>	<4D08FB7D.2010702@codemonkey.ws>	<m339pyyl59.fsf@blackfin.pond.sub.org> <4D10C4B2.9000401@redhat.com>	<m362unkub4.fsf@blackfin.pond.sub.org>	<20101221160032.GG28002@amd.home.annexia.org> <m3d3ovgldr.fsf@blackfin.pond.sub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Richard W.M. Jones" <rjones@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>,
	kvm@vger.kernel.org
To: Markus Armbruster <armbru@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-vw0-f46.google.com ([209.85.212.46]:56915 "EHLO
	mail-vw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750874Ab0LUQ4z (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 21 Dec 2010 11:56:55 -0500
Received: by vws16 with SMTP id 16so1774952vws.19
        for <kvm@vger.kernel.org>; Tue, 21 Dec 2010 08:56:54 -0800 (PST)
In-Reply-To: <m3d3ovgldr.fsf@blackfin.pond.sub.org>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 12/21/2010 10:07 AM, Markus Armbruster wrote:
> "Richard W.M. Jones"<rjones@redhat.com>  writes:
>
>    
>> On Tue, Dec 21, 2010 at 04:41:03PM +0100, Markus Armbruster wrote:
>>      
>>> Like this?
>>>
>>> upstream qemu   |  default  |-enable-kvm
>>> ----------------+-----------+-----------
>>> KVM available   | disabled  |  enabled
>>> KVM unavailable | disabled  |    fail
>>>
>>> qemu-kvm        |  default  |-enable-kvm|  -no-kvm
>>> ----------------+-----------+-----------+-----------
>>> KVM available   |  enabled* |  enabled  |  disabled
>>> KVM unavailable | disabled  |    fail   |  disabled
>>>
>>> * differs from upstream
>>>        
>> libguestfs wants "best effort" behaviour, and libvirt wants "KVM or die"
>> behaviour.
>>      
> For what it's worth, default gives you exactly that with qemu-kvm.
> Maybe that's good enough, on the theory that if you have KVM, you most
> likely have libguestfs using qemu-kvm.
>
>    
>> Avi, can you comment on whether just opening /dev/kvm O_RDWR is a
>> reasonable way to detect if KVM is available?
>>
>> Markus, any idea when we might get the -accel option appearing in
>> released versions of qemu/KVM?
>>      
> No idea.  Anthony?
>    

I see no problem with 0.15 if someone cooks up a patch.

Regards,

Anthony Liguori