From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Webb Subject: Re: qemu-kvm segfaults in qemu_del_timer (0.10.5 and 0.10.6) Date: Thu, 13 Aug 2009 13:45:46 +0100 Message-ID: <20090813124546.GB21678@arachsys.com> References: <20090812150159.GW5348@arachsys.com> <4A82E200.3040107@redhat.com> <20090812162401.GB8115@arachsys.com> <20090813122333.GA2863@arachsys.com> <4A840A3E.1040400@redhat.com> <20090813124350.GA21678@arachsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org To: Avi Kivity Return-path: Received: from alpha.arachsys.com ([91.203.57.7]:35732 "EHLO alpha.arachsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754460AbZHMMtv (ORCPT ); Thu, 13 Aug 2009 08:49:51 -0400 Content-Disposition: inline In-Reply-To: <20090813124350.GA21678@arachsys.com> Sender: kvm-owner@vger.kernel.org List-ID: Chris Webb writes: > Avi Kivity writes: > > > csock looks corrupted, should be -1 or an fd. Was a vnc client connected? > > Was the guest playing with the display resolution? > > Yes, I think in this case there was a vncviewer connected, and the guest had > started booting up into windows, which changes the resolution a couple of > times. Also, I think the vncviewer might actually have been disconnecting at about the time the segfault happened. Cheers, Chris.