public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: -smp >=2 + -no-kvm-irqchip broken
Date: Thu, 04 Feb 2010 01:42:38 +0100	[thread overview]
Message-ID: <4B6A17FE.4090203@web.de> (raw)
In-Reply-To: <20100203125659.GM739@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]

Gleb Natapov wrote:
> On Tue, Feb 02, 2010 at 07:56:42PM +0100, Jan Kiszka wrote:
>> Jan Kiszka wrote:
>>> Gleb Natapov wrote:
>>>> On Tue, Feb 02, 2010 at 05:41:03PM +0100, Jan Kiszka wrote:
>>>>> Gleb Natapov wrote:
>>>>>> On Tue, Feb 02, 2010 at 05:29:53PM +0100, Jan Kiszka wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> notice while testing v2 of my vcpu state series: Starting SMP guests
>>>>>>> like Linux or Vista without in-kernel irqchip and with more than one CPU
>>>>>>> make them lock up during boot (Vista) or spit out messages like
>>>>>>>
>>>>>>> udevd[112] trap invalid opcode ip:7fc434630950 sp:7fff3cd3fcb8 error:0
>>>>>>> in libc-2.9.so[7fc4345b2000+14f000]
>>>>>>>
>>>>>> Looks like interrupt is injected as exception. Can you try to bisect?
>>>>> Already started (as low prio background task), first looking for a good
>>>>> version. If you know a recent one, I'm a taker.
>>>>>
>>>> Nope, didn't try no kernel irqchip for a long time.
>>> Kernel plays the key role here, either kvm-kmod or actually the kvm
>>> module: kvm-kmod-2.6.31.6 works, the 2.6.32 series and later do not.
>>> Digging deeper...
>> I take this back: It works for Linux guests, but Vista crashes also with
>> old kvm-kmod. So there is no way around real debugging.
>>
> Upstream qemu-kvm/kvm works for me. Boot linux with -smp 2 and
> windows2008-32 with -smp 4.

We seem to have two issues:
 - kvm.git master breaks 64-bit linux guests under -no-kvm-irqchip +
   smp (#UD pop up in guest user space). 2.6.33 kvm is fine. Will try to
   bisect this the next days.
 - My Vista x64 image apparently suffer from a race (I suspect in user
   space) that lets it deadlock on a spinlock, independent of the
   underlying kernel kvm version.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

      reply	other threads:[~2010-02-04  0:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 16:29 -smp >=2 + -no-kvm-irqchip broken Jan Kiszka
2010-02-02 16:39 ` Gleb Natapov
2010-02-02 16:41   ` Jan Kiszka
2010-02-02 16:47     ` Gleb Natapov
2010-02-02 18:52       ` Jan Kiszka
2010-02-02 18:56         ` Jan Kiszka
2010-02-03 12:56           ` Gleb Natapov
2010-02-04  0:42             ` Jan Kiszka [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=4B6A17FE.4090203@web.de \
    --to=jan.kiszka@web.de \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.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