From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kasper Sandberg Subject: Re: kvm kernel backtrace 2.6.27.3 using kvm 78 userspace Date: Sun, 23 Nov 2008 17:16:15 +0100 Message-ID: <1227456976.19624.115.camel@localhost> References: <1227386974.19624.103.camel@localhost> <49291904.5000607@redhat.com> <1227450233.19624.113.camel@localhost> <4929684A.7030704@redhat.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from pasmtpa.tele.dk ([80.160.77.114]:50855 "EHLO pasmtpA.tele.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755161AbYKWQQR (ORCPT ); Sun, 23 Nov 2008 11:16:17 -0500 In-Reply-To: <4929684A.7030704@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Sun, 2008-11-23 at 16:27 +0200, Avi Kivity wrote: > Kasper Sandberg wrote: > >> What guest are you running? > >> > > > > Yeah sorry, i was gonna include that in the mail, i apparently forgot. > > > > I have been running debian, both 32 and 64bit inside it, .18, .24 > > and .26 kernels, and ubuntu 8.10 .27 kernels, ATLEAST 32bit, i do not > > remember if i have run 64bit ubuntu 8.10 > > > > I can however give some information that _MIGHT_ (i have no clue myself) > > be relevant > > > > on one of the debian guests i had xrandr crash the X server while trying > > to change resolution, i did this a few times. Using -vga std. > > > > also, on the ubuntu 32bit guest, i ran qemu with debian stable, where X > > crashed during start inside the qemu on the ubuntu guest. This happened > > only once. > > > > im quite certain my ram and that is fine, no errors when doing memory > > testing etc. > > > > > > but as said, the kernel is tainted, i dont know if that affects the > > results or not, i just wanted to inform in case this can help someone. > > That being said, the box has NOT been rebooted since, and i can confirm > > that kvm works excellently, i have spawned several VMs and used a tad, > > since i wrote the mail > > Well, if you can find a recipe that reliably reproduces the problems, we > want to hear of it. Within the coming week i will try to find the time to update to latest kernel/kvm, and then do all the things i remember doing in the VMs, to try and reproduce >