qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@gmail.com>
To: Dustin Kirkland <kirkland@canonical.com>
Cc: Mark McLoughlin <markmc@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH] qemu-kvm: fix segfault when running kvm without /dev/kvm, falling back to non-accelerated mode
Date: Thu, 3 Sep 2009 19:18:24 -0300	[thread overview]
Message-ID: <5d6222a80909031518h2bf804fbk1f7a52424d3e8649@mail.gmail.com> (raw)
In-Reply-To: <d9c105ea0909031448v4d727c1cpaaa60d1e28820660@mail.gmail.com>

On Thu, Sep 3, 2009 at 6:48 PM, Dustin Kirkland<kirkland@canonical.com> wrote:
> On Thu, Sep 3, 2009 at 3:01 PM, Mark McLoughlin<markmc@redhat.com> wrote:
>> On Thu, 2009-09-03 at 12:31 -0500, Dustin Kirkland wrote:
>>> qemu-kvm: fix segfault when running kvm without /dev/kvm, falling back
>>> to non-accelerated mode
>>>
>>> We're seeing segfaults on systems without access to /dev/kvm.  It
>>> looks like the global kvm_allowed is being set just a little too late
>>> in vl.c.  This patch moves the kvm initialization a bit higher in the
>>> vl.c main, just after options processing, and solves the segfaults.
>>> We're carrying this patch in Ubuntu 9.10 Alpha.  Please apply
>>> upstream, or advise if and why this might not be the optimal solution.
>>
>> Ah discussion about an alternative fix for this fizzled out recently:
>>
>>  http://www.mail-archive.com/kvm@vger.kernel.org/msg19890.html
>
> Ah, thanks Mark.  In that thread, I found Daniel's suggestion the most
> reasonable, and user-friendly:
>
> On Mon, Jul 27, 2009 at 1:44 PM, Daniel P. Berrange<berrange@redhat.com> wrote:
>> Well, we could go for logic like:
>>
>>  * No arg given          => try kvm, try kqemu, try tcg
>>  * --accelmode arg given => try $arg, and fail if unavailable
>>
>> then libvirt would simply always supply --accelmode for all VMs,
>> while people running qemu manually would get best available
I sent some patches to do that, but they were incomplete, and I was
preempted by something else.
If you want, you can wait for my cycles to come back, or pick from where I left



-- 
Glauber  Costa.
"Free as in Freedom"
http://glommer.net

"The less confident you are, the more serious you have to act."

  reply	other threads:[~2009-09-03 22:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03 17:31 [Qemu-devel] [PATCH] qemu-kvm: fix segfault when running kvm without /dev/kvm, falling back to non-accelerated mode Dustin Kirkland
2009-09-03 19:55 ` [Qemu-devel] " Marcelo Tosatti
2009-09-03 20:01 ` Mark McLoughlin
2009-09-03 21:48   ` Dustin Kirkland
2009-09-03 22:18     ` Glauber Costa [this message]
2009-09-04  7:22       ` Mark McLoughlin
2009-09-04 16:06         ` Dustin Kirkland
2009-09-04 16:36           ` Marcelo Tosatti
2009-09-04 19:38             ` Dustin Kirkland
2009-09-04 21:39               ` Luiz Capitulino
2009-09-04 21:46                 ` Marcelo Tosatti
2009-09-04 22:03                   ` Luiz Capitulino
2009-09-03 20:05 ` Luiz Capitulino

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=5d6222a80909031518h2bf804fbk1f7a52424d3e8649@mail.gmail.com \
    --to=glommer@gmail.com \
    --cc=kirkland@canonical.com \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).