From mboxrd@z Thu Jan 1 00:00:00 1970 From: Farkas Levente Subject: Re: [ANNOUNCE] kvm-48 release Date: Fri, 19 Oct 2007 15:35:44 +0200 Message-ID: <4718B2B0.9050909@bppiac.hu> References: <471790A3.5080704@qumranet.com> <47186186.5070409@bppiac.hu> <47187245.3020201@bppiac.hu> <471874AD.4080201@bull.net> <47189897.508@bppiac.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: kvm-devel , Avi Kivity To: Laurent Vivier Return-path: In-Reply-To: <47189897.508-lWVWdrzSO4GHXe+LvDLADg@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 Farkas Levente wrote: > Laurent Vivier wrote: >> Farkas Levente a =E9crit : >>> Farkas Levente wrote: >>>> Avi Kivity wrote: >>>>> kvm-47 had a host memory corruption bug when setting the guest pte >>>>> dirty bit, so here's kvm-48 with a fix. >>>>> >>>>> Note that guest time accounting, below, will only work with Linux >>>>> 2.6.24+. >>>> smp guests still not working with kvm-48:-( i can't image what others >>>> can do to make it work. guests hang at random stage during boot. i >>>> attached guests boot screenshot. 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 >>>> ------------------------------------------------ >>>> i try guest-1 and huest-2 with 4 vcpu others with 1 vcpu. >>>> on host the only thing i've got in dmesg: >>>> ------------------------------------------------ >>>> 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+0xfb/0x109 >>>> [] :kvm:kvm_flush_remote_tlbs+0xea/0x109 >>>> [] :kvm:gfn_to_page+0xa3/0xd5 >>>> [] :kvm:mark_page_dirty+0x9/0x2a >>>> [] :kvm:kvm_mmu_pte_write+0x1fc/0x330 >>>> [] :kvm:emulator_write_emulated_onepage+0x6e/0xce >>>> [] :kvm:x86_emulate_insn+0x2b98/0x4134 >>>> [] __handle_mm_fault+0x832/0xdf2 >>>> [] :kvm_intel:vmcs_readl+0x17/0x1c >>>> [] :kvm:emulate_instruction+0x152/0x290 >>>> [] :kvm_intel:handle_exception+0x170/0x250 >>>> [] :kvm:kvm_vcpu_ioctl+0x343/0xf43 >>>> [] try_to_wake_up+0x407/0x418 >>>> [] __wake_up_common+0x3e/0x68 >>>> [] __wake_up+0x38/0x4f >>>> [] __up_read+0x19/0x7f >>>> [] avc_has_perm+0x43/0x55 >>>> [] inode_has_perm+0x56/0x63 >>>> [] getnstimeofday+0x10/0x28 >>>> [] default_wake_function+0x0/0xe >>>> [] file_has_perm+0x94/0xa3 >>>> [] do_ioctl+0x21/0x6b >>>> [] vfs_ioctl+0x248/0x261 >>>> [] sys_ioctl+0x59/0x78 >>>> [] tracesys+0xd1/0xdc >>>> ------------------------------------------------ >>> the situation is even worse, the guests are hang during boot even with >>> single vcpu and even with kvm-46:-( i attached another screenshot. but >>> after i kill the guest and start it again it works. it seems the problem >>> occurs when i start more guest at the same time (eg. after reboot the >>> host). and it seems there is some kind of acpi error since all of the >>> guest hang screenshot contains some kind of acpi error. >> What happens if you use "-noacpi" ? > = > in this case single cpu guests are working with kvm-48, but 4 > vcpu/guests still hang:-( one more thing which happened with single cpu guests on kvm-48 in dmesg on the host: Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring Fault when IDT_Vectoring -- = Levente "Si vis pacem para bellum!" ------------------------------------------------------------------------- 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/