From mboxrd@z Thu Jan 1 00:00:00 1970 From: William Boughton Subject: Re: guests locking up issue Date: Wed, 18 Jun 2008 11:34:37 +0200 Message-ID: <20080618093437.GA13133@yuri.org.uk> References: <200806171429.59706.iggy@theiggy.com> <20080617224210.GA24642@yuri.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: kvm@vger.kernel.org Return-path: Received: from soapstone.yuri.org.uk ([78.47.151.105]:51460 "EHLO soapstone.yuri.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752015AbYFRJej (ORCPT ); Wed, 18 Jun 2008 05:34:39 -0400 Received: from murble by soapstone.yuri.org.uk with local (Exim 4.68) (envelope-from ) id 1K8u3p-0006AA-UK for kvm@vger.kernel.org; Wed, 18 Jun 2008 10:34:37 +0100 Content-Disposition: inline In-Reply-To: <20080617224210.GA24642@yuri.org.uk> Sender: kvm-owner@vger.kernel.org List-ID: > with KVM-70 > > my host: > dual quad core Intel E5320 > 4G ram > Debian Etch > 2.6.26-rc6 x86_64 > > my guest: > debian etch > 2.6.26-rc6 x86_64 > 512 Mb ram I rebuild my guest kernels without CONFIG_KVM_CLOCK, just with CONFIG_HAVE_KVM=y It now seems far more stable with -smp 4 > started with: > > qemu-system-x86_64 -drive \ > file=/mnt/kvms/images/guitest.img,if=ide,boot=on -m 512 \ > -vnc localhost:2 -name guitest -monitor stdio -net \ > nic,model=e1000,macaddr=00:12:8E:BA:AC:22 -net \ > tap,script=/etc/qemu-ifup,ifname=tapguitest -k en-gb -smp 4 > > further details of my setup including .configs are at > http://www.yuri.org.uk/~murble/kvm/ > > I'm also able to reproduce this with the same image on a > dual Quad-Core AMD Opteron(tm) Processor 2354 with 16Gb of RAM. I left two guest running all night building kernels in a loop with -j3 and -smp 4 using both virtio-blk and net. One running on the Intel quad core machine the other on the AMD quadcore machine running the same guest image file, kvm version and guest kernel version. Some time in the night the Intel guest froze the AMD hosted one is still going strong. The Intel host is hosting some other KVM guests without virtio / smp which had bad been running several days until I upgraded to 2.6.26-rc6 yesterday evening without any crashes. The guest running on Intel qemu monitor is still responsive but the qemu-system-x86 was using 200% CPU constantly. both guests were started with: qemu-system-x86_64 -drive \ file=/mnt/kvms/images/guitest.img,if=virtio,boot=on -m 512 -vnc \ localhost:2 -name guitest -monitor stdio -net \ nic,model=virtio,macaddr=00:12:8E:BA:AC:22 -net \ tap,script=/etc/qemu-ifup,ifname=tapguitest -k en-gb -smp 4 Details of the amd host configuration are at http://www.yuri.org.uk/~murble/kvm/amd/ When I quit from the qemu monitor on the intel host i got a softlockup on the host http://www.yuri.org.uk/~murble/kvm/intel-host-softlockup.txt my new guest .config http://www.yuri.org.uk/~murble/kvm/new.guest.config.txt used on both guests. regards bill -- Bill Boughton