public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Gianluca Cecchi
	<gianluca.cecchi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: kvm 35 and 36 segfault when smp 2 or more
Date: Tue, 04 Sep 2007 23:12:43 +0300	[thread overview]
Message-ID: <46DDBC3B.2030101@qumranet.com> (raw)
In-Reply-To: <561c252c0709041542m8aa735ena992c3ba585d1873-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Gianluca Cecchi wrote:
> System is a quadcore intel with Fedora 7 x86_64
> tried with latest ok kernel 2.6.22.4-65.fc7 and the one in testing: 
> 2.6.22.5-71.fc7
> tried with latest kvm 24 in F7, then with kvm-35 in testing then 
> compiling kvm-36 (with same .spec of fedora one)
> qemu-kvm -cdrom F-7.90-x86_64-rescuecd.iso -boot d -smp 1
> is ok (also without smp switch at all that should be the same)
> with -smp 2
> I get
> kvm_create_vcpu: Invalid argument
> kvm_get_msrs FAILED: Invalid argument
> kvm_set_msrs FAILED: Invalid argument
> Segmentation fault
> and in dmesg
> Sep  5 00:04:20 localhost kernel: qemu-kvm[3655]: segfault at 
> 0000000000000000 r
> ip 00000000004de19d rsp 00000000409fff90 error 6
>
> with -smp 3 one more kvm_create_vcpu: Invalid argument error and
> qemu-kvm[4102]: segfault at 0000000000000000 rip 00000000004de19d rsp 
> 0000000041400f90 error 6
>
> the same for example with x86 winxp iso img
> qemu-system-x86_64 works ok and if I go in console and do "info cpus"
> I can find
> * cpu#0: pc=0x000000000000e84
>   cpu#1: pc=0x0000000000010009 (halted)
>
> any hints on having kvm smp guest working?
>
> BTW: in one thread of this list I saw that, if I understood right, it 
> should be safe now not to use --with-patched-kernel with kernels 
> greater than 2.6.22 (as mine is) and that this was valid when kvm was 
> only in -mm tree
> In Fedora spec the configure step is yet
> ./configure --with-patched-kernel --qemu-cc=gcc34 
> --kerneldir=$(pwd)/kernel --prefix=%{_prefix}
>
is it mean you didnt compile the new kernel modules?
the linux 2.6.22 kvm does not support smp, dont use the 
--with-patched-kernel
and after building kvm-36 do: rmmod kvm_intel rmmod kvm
insmod kernel/kvm.ko insmod kernel/kvm-intel.ko and try it now.



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  parent reply	other threads:[~2007-09-04 20:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-04 22:42 kvm 35 and 36 segfault when smp 2 or more Gianluca Cecchi
     [not found] ` <561c252c0709041542m8aa735ena992c3ba585d1873-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-04 20:12   ` Izik Eidus [this message]
     [not found]     ` <46DDBC3B.2030101-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-05  8:27       ` Gianluca Cecchi
     [not found]         ` <561c252c0709050127l11a9cdd7g3f6696fa7f3051e8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-06 22:30           ` Gianluca Cecchi
2007-09-05  3:35   ` Alexey Eremenko

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=46DDBC3B.2030101@qumranet.com \
    --to=izike-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=gianluca.cecchi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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