public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
* kvm 35 and 36 segfault when smp 2 or more
@ 2007-09-04 22:42 Gianluca Cecchi
       [not found] ` <561c252c0709041542m8aa735ena992c3ba585d1873-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
  0 siblings, 1 reply; 5+ messages in thread
From: Gianluca Cecchi @ 2007-09-04 22:42 UTC (permalink / raw)
  To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f


[-- Attachment #1.1: Type: text/plain, Size: 2078 bytes --]

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}

and my failing kvm rpms are configured this way
but if I use instead
./configure  --qemu-cc=gcc34  --prefix=%{_prefix}
I finally get a message like
error: Installed (but unpackaged) files found:
with the compiled kvm kernel modules in the list.....
so it seems that it tries to overwrite your kernel ones...??? but shouldn't
they be ok????
or I don't understand

and if I use
./configure --qemu-cc=gcc34 --kerneldir=$(pwd)/kernel --prefix=%{_prefix}

the build process goes in an infinite loop (forks I presume) where if I
don't press Ctrl-C in time, the system freezes and I have to manually press
power switch to shutdown....
Thanks for your help,
Gianluca

[-- Attachment #1.2: Type: text/html, Size: 2267 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2007-09-06 22:30 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
     [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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox