From mboxrd@z Thu Jan 1 00:00:00 1970 From: david ahern Subject: Re: [ANNOUNCE] kvm-51 release Date: Sun, 11 Nov 2007 08:32:00 -0700 Message-ID: <47372070.30604@cisco.com> References: <4731F5B5.1000108@qumranet.com> <473435B6.1000503@bppiac.hu> <4736C752.7060703@qumranet.com> <4736FC77.2080804@bppiac.hu> <47371510.3020804@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Cc: kvm-devel To: Avi Kivity Return-path: In-Reply-To: <47371510.3020804-atKUWr5tajBWk0Htik3J/w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org I now have hosts running both 32-bit and 64-bit versions of RHEL5.1. I will= retry SMP guests on the RHEL5 kernel, but at present kvm-51 does not compi= le: make -C kernel make[1]: Entering directory `/opt/kvm/kvm-51/kernel' make -C /lib/modules/2.6.18-53.el5/build M=3D`pwd` "$@" make[2]: Entering directory `/usr/src/kernels/2.6.18-53.el5-i686' LD /opt/kvm/kvm-51/kernel/built-in.o CC [M] /opt/kvm/kvm-51/kernel/svm.o CC [M] /opt/kvm/kvm-51/kernel/vmx.o CC [M] /opt/kvm/kvm-51/kernel/vmx-debug.o CC [M] /opt/kvm/kvm-51/kernel/kvm_main.o /opt/kvm/kvm-51/kernel/kvm_main.c: In function =91kvm_cpu_hotplug=92: /opt/kvm/kvm-51/kernel/kvm_main.c:1348: error: =91CPU_UP_CANCELED_FROZEN=92= undeclared (first use in this function) /opt/kvm/kvm-51/kernel/kvm_main.c:1348: error: (Each undeclared identifier = is reported only once /opt/kvm/kvm-51/kernel/kvm_main.c:1348: error: for each function it appears= in.) make[3]: *** [/opt/kvm/kvm-51/kernel/kvm_main.o] Error 1 make[2]: *** [_module_/opt/kvm/kvm-51/kernel] Error 2 make[2]: Leaving directory `/usr/src/kernels/2.6.18-53.el5-i686' make[1]: *** [all] Error 2 make[1]: Leaving directory `/opt/kvm/kvm-51/kernel' make: *** [kernel] Error 2 david Avi Kivity wrote: > Farkas Levente wrote: >> Avi Kivity wrote: >> = >>> Farkas Levente wrote: >>> = >>>> Avi Kivity wrote: >>>> = >>>> = >>>>> If you're having trouble on AMD systems, please try this out. >>>>> = >>>>> = >>>> this version worse than kvm-50:-( >>>> setup: >>>> - host: >>>> - Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz >>>> - Intel S3000AHV >>>> - 8GB RAM >>>> - CentOS-5 >>>> - kernel-2.6.18-8.1.14.el5 x86_64 64bit >>>> - guest-1: >>>> - CentOS-5 >>>> - kernel-2.6.18-8.1.14.el5 i386 32bit >>>> - guest-2: >>>> - CentOS-5 >>>> - kernel-2.6.18-8.1.14.el5 x86_64 64bit >>>> - guest-3: >>>> - Mandrake-9 >>>> - kernel-2.4.19.16mdk-1-1mdk 32bit >>>> - guest-4: >>>> - Windows XP Professional 32bit >>>> smp not working on any centos guest (guests are hang during boot). even >>>> the host crash. the worst thing is the host crash during boot with >>>> another stack trace which i was not able to log. >>>> i really would like to see some kind of stable version other then >>>> kvm-36. i see there is a huge ongoing work on ia64, virtio, libkmv and >>>> arch rearrange, but wouldn't it be better to fix these basic issues >>>> first? like running two smp guest (32 and 64) on 64 smp host, just to >>>> boot until the login screen. >>>> this is when the guest stop and the host dump it: >>>> = >>>> = >>> [...] >>> >>> = >>>> Call Trace: >>>> [] softlockup_tick+0xdb/0xed >>>> [] update_process_times+0x42/0x68 >>>> [] smp_local_timer_interrupt+0x23/0x47 >>>> [] smp_apic_timer_interrupt+0x41/0x47 >>>> [] apic_timer_interrupt+0x66/0x6c >>>> [] :kvm:kvm_flush_remote_tlbs+0x16e/0x188 >>>> [] :kvm:kvm_flush_remote_tlbs+0x15b/0x188 >>>> [] :kvm:ack_flush+0x0/0x1 >>>> = >>>> = >>> Are you sure this is a regression relative to kvm-50? Please recheck. >>> = >> i', not sure this's a regression since kvm-50 was so terrible slow that >> we switch back to kvm-46. but i can't catch any stack trace with kvm-50. >> anyway even if it's not a regression it's currently not working with smp. >> >> = > = > I can't reproduce this on a centos system here running 2.6.18-8.el5 with = > a 4-way FC6 x86_64 as guest. It appears to survive a kernel compile. > = > What does one need to do in order to reproduce this? > = ------------------------------------------------------------------------- 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/