Re: kvm 35 and 36 segfault when smp 2 or more

Re: kvm 35 and 36 segfault when smp 2 or more

[Izik Eidus]

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/

kvm 35 and 36 segfault when smp 2 or more

[Gianluca Cecchi]

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

Re: kvm 35 and 36 segfault when smp 2 or more

[Alexey Eremenko]

What is your CPU ?

-- 
-Alexey Eremenko "Technologov"

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

Re: kvm 35 and 36 segfault when smp 2 or more

[Gianluca Cecchi]

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

Ok, I added the kernel modules lines in %files section of spec file and
built successfully kvm-36 with
./configure --qemu-cc=gcc34 --prefix=%{_prefix}
then I installed the rpm overwriting the default kernel modules and I'm able
to run with smp 2
I successfully booted an F8 live x86_64 rescue cd image and a F7 i386 DVD
image.

I will test further...

Thanks for the moment!
Gianluca

On 9/4/07, Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>
>
> 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.
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 1074 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

Re: kvm 35 and 36 segfault when smp 2 or more

[Gianluca Cecchi]

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

answering to Alexey: it is a QX6700
cat /proc/cpuinfo gives 4 X

processor       : x
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz
stepping        : 7
cpu MHz         : 1596.000
cache size      : 4096 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm
constant_tsc
 pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips        : 5336.07
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

Gianluca

[-- Attachment #1.2: Type: text/html, Size: 1627 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