From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [qemu bug] device assignment doesn't work: "error: requires KVM support" Date: Thu, 27 Oct 2011 09:38:02 +0200 Message-ID: <4EA90A5A.4080204@web.de> References: <1319684651.19108.106.camel@bling.home> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigADE0926341BDA995AA8634B0" Cc: "Ren\, Yongjie" , Alex Williamson , KVM General , Avi Kivity To: Markus Armbruster Return-path: Received: from fmmailgate04.web.de ([217.72.192.242]:44543 "EHLO fmmailgate04.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752434Ab1J0Hrg (ORCPT ); Thu, 27 Oct 2011 03:47:36 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigADE0926341BDA995AA8634B0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-10-27 09:20, Markus Armbruster wrote: > "Ren, Yongjie" writes: >=20 >>> -----Original Message----- >>> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org] On= >>> Behalf Of Ren, Yongjie >>> Sent: Thursday, October 27, 2011 3:03 PM >>> To: Markus Armbruster >>> Cc: Alex Williamson; KVM General; Avi Kivity >>> Subject: RE: [qemu bug] device assignment doesn't work: "error: requi= res KVM >>> support" >>> >>>> -----Original Message----- >>>> From: Markus Armbruster [mailto:armbru@redhat.com] >>>> Sent: Thursday, October 27, 2011 2:50 PM >>>> To: Ren, Yongjie >>>> Cc: Alex Williamson; KVM General; Avi Kivity >>>> Subject: Re: [qemu bug] device assignment doesn't work: "error: requ= ires KVM >>>> support" >>>> >>>> "Ren, Yongjie" writes: >>>> >>>>>> -----Original Message----- >>>>>> From: Alex Williamson [mailto:alex.williamson@redhat.com] >>>>>> Sent: Thursday, October 27, 2011 11:04 AM >>>>>> To: Ren, Yongjie >>>>>> Cc: KVM General; Avi Kivity >>>>>> Subject: Re: [qemu bug] device assignment doesn't work: "error: re= quires >>>> KVM >>>>>> support" >>>> [...] >>>>>> The error message is correct, device assignment requires kvm suppo= rt. >>>>>> What does 'info kvm' in the monitor report? >>>>> It shows "kvm support: disabled". >>>>> But when configuring qemu, I get this message " KVM support yes". S= ee >>> details >>>> in my attachment configure.log >>>> >>>> Try running with --enable-kvm. >>> >>> I added '--enable-kvm' when configuring qemu. I got the same configur= e output. >>> And I compiled and ran qemu, then I met the same issue as I describle= d before. >> Oh, adding '--enable-kvm' when running qemu will work. The following c= ommand line enables kvm when qemu starting. >> ./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device pci-assign,= host=3D0e:00.0 -hda /root/rhel6u1.img --enable-kvm >> But it didn't need to add '--enable-kvm' two weeks ago. Must we add th= is parameter from now on if we want to use kvm ? >=20 > 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 --------------enigADE0926341BDA995AA8634B0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6pCloACgkQitSsb3rl5xTzMACgiXweYnwt3tJldR+dvGnYYWlU LDMAoLMsqKEUZmFYzuEcgPR9P9gKcX4w =VXey -----END PGP SIGNATURE----- --------------enigADE0926341BDA995AA8634B0--