From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [qemu bug] device assignment doesn't work: "error: requires KVM support" Date: Thu, 27 Oct 2011 10:36:29 -0200 Message-ID: <20111027123629.GD29646@amt.cnet> References: <1319684651.19108.106.camel@bling.home> <4EA90A5A.4080204@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Markus Armbruster , "Ren, Yongjie" , Alex Williamson , KVM General , Avi Kivity To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:63076 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755313Ab1J0Mhp (ORCPT ); Thu, 27 Oct 2011 08:37:45 -0400 Content-Disposition: inline In-Reply-To: <4EA90A5A.4080204@web.de> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Oct 27, 2011 at 09:38:02AM +0200, Jan Kiszka wrote: > >> But it didn't need to add '--enable-kvm' two weeks ago. Must we add this parameter from now on if we want to use kvm ? > > > > Use of KVM should still be the default. If it isn't anymore, can you > > use bisect to finger the commit that broke it? > > Might be "qemu-kvm: set default accelerator via target.conf". Unless you > fully install qemu, that conf is not picked up (or an older version is > used). I'd still like to see this working with qemu started from a build > directory... > > Jan Actually it was lack of 0eb2a7e9010f2 since he was using 8843cf40. But you're right, reverted a5c40eb1aa9 for now, thanks.