From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Jackson Subject: Re: user: time jump in slave machine leads to freeze Date: Tue, 25 Jan 2011 11:57:48 -0600 Message-ID: <4D3F0F1C.4070603@theiggy.com> References: <717572.90356.qm@web29502.mail.ird.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: gnafou Return-path: Received: from theiggy.com ([66.220.1.110]:33042 "EHLO mail.theiggy.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752914Ab1AYSHM (ORCPT ); Tue, 25 Jan 2011 13:07:12 -0500 In-Reply-To: <717572.90356.qm@web29502.mail.ird.yahoo.com> Sender: kvm-owner@vger.kernel.org List-ID: On 1/25/2011 9:21 AM, gnafou wrote: > Hello > > We have had several cases where a slave machine freezes, eating all available > cpu. ( this happends randomly, say, after 3 months of correct functionning ) > > After reboot, looking at the syslog when the freeze occured, the few ( ~5 ) > last lines written show a date which has jumped in the future ( roughly, 15 days > ahead ), but nothing related to the crash is logged. > > our salves machines are ntp-synchronized > > > we run under debian/lenny > we launch the machines with the kvm command > > kernel of host : 2.6.26-2-amd64 > kernel of host : 2.6.26-2-686 I'm pretty sure this issue has been fixed in newer versions of qemu-kvm and the kernel. You might want to try using the versions from backports. You are unlikely to get much support on a kernel that's 10 releases old and iirc, the kvm that came with lenny was only a development snapshot. > command launched : > > kvm -name svn -drive file=xxx -net tap -m 256 -net nic,macaddr=xxx -pidfile > /var/run/kvm/xx.pid -daemonize -k fr -vnc :63006 -monitor > unix:xx_monitor,server,nowait -vnc unix:xx_vnc > > > If you ever have an idea how to solve or to debug the problem ... > > Thanks > > > Fred > > > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html