kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Markus Armbruster <armbru@redhat.com>,
	"Ren, Yongjie" <yongjie.ren@intel.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	KVM General <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [qemu bug] device assignment doesn't work: "error: requires KVM support"
Date: Thu, 27 Oct 2011 10:36:29 -0200	[thread overview]
Message-ID: <20111027123629.GD29646@amt.cnet> (raw)
In-Reply-To: <4EA90A5A.4080204@web.de>

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.


  reply	other threads:[~2011-10-27 12:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27  2:56 [qemu bug] device assignment doesn't work: "error: requires KVM support" Ren, Yongjie
2011-10-27  3:04 ` Alex Williamson
2011-10-27  3:17   ` Ren, Yongjie
2011-10-27  6:49     ` Markus Armbruster
2011-10-27  7:03       ` Ren, Yongjie
2011-10-27  7:12         ` Ren, Yongjie
2011-10-27  7:20           ` Markus Armbruster
2011-10-27  7:38             ` Jan Kiszka
2011-10-27 12:36               ` Marcelo Tosatti [this message]
2011-10-27  7:18         ` Markus Armbruster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111027123629.GD29646@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=armbru@redhat.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=yongjie.ren@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).