From: Avi Kivity <avi@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: SIGSEGV with -smp 17+, and error handling around...
Date: Wed, 24 Mar 2010 14:11:21 +0200 [thread overview]
Message-ID: <4BAA0169.7000707@redhat.com> (raw)
In-Reply-To: <4BA13794.9080401@msgid.tls.msk.ru>
On 03/17/2010 10:12 PM, Michael Tokarev wrote:
> When run with -smp 17 or greather, kvm
> fails like this:
>
> $ kvm -smp 17
> kvm_create_vcpu: Invalid argument
> kvm_setup_mce FAILED: Invalid argument
> KVM_SET_LAPIC failed
> Segmentation fault
> $ _
>
> In qemu-kvm.c, the kvm_create_vcpu() routine
> (which is used in a vcpu thread to set up
> vcpu) is declared as void, i.e, no error
> return. And the code that calls it blindly
> assumes that it will never fail...
>
> But the first error message above is from kernel,
> which - apparently - refuses to create 17th vCPU.
> Hence we've a vcpu thread which is empty/dummy and
> not even fully initialized... so it fails later
> in the game.
>
> This all looks quite... raw, not polished ;)
>
> Can we somehow handle the (several possible) errors
> in that (and other) places, and how we ever can act
> on them? Abort? Warn the user and reduce the number
> of vcpus accordingly (seems wrong, esp. if it were
> some first vcpus or in the middle which failed)...
>
A patch from Alex fixing this was just committed. I'll apply it to the
stable branch as well.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-03-24 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 20:12 SIGSEGV with -smp 17+, and error handling around Michael Tokarev
2010-03-24 12:11 ` Avi Kivity [this message]
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=4BAA0169.7000707@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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.