All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Bruce Rogers <brogers@novell.com>
Subject: Re: [Qemu-devel] [PATCH] limit guest cpus for kvm enabled builds
Date: Thu, 9 Apr 2009 17:05:19 +0100	[thread overview]
Message-ID: <200904091705.20024.paul@codesourcery.com> (raw)
In-Reply-To: <49DDC4160200004800071C73@lucius.provo.novell.com>

On Thursday 09 April 2009, Bruce Rogers wrote:
> The x86 kvm kernel module limits guest cpu count to 16, but the userspace
> pc definition says 255 still.  When invoking qemu-kvm with -smp > 16, it
> prints some error messages, then segfaults.   One of the mistakes is that
> the error code from kvm_create_vcpu is ignored in ap_main_loop. 

You should fix that bug then.

> This patch will enforce the limit at initialization time and avoid these
> problems from the get go.

No. We still want to support a decent number of cpus when -no-kvm is 
specified.

Paul

  reply	other threads:[~2009-04-09 16:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 15:47 [Qemu-devel] [PATCH] limit guest cpus for kvm enabled builds Bruce Rogers
2009-04-09 16:05 ` Paul Brook [this message]
2009-04-09 16:44   ` Anthony Liguori
2009-04-09 17:27     ` Bruce Rogers

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=200904091705.20024.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=brogers@novell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.