From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: just a dump Date: Sat, 23 May 2009 18:47:53 -0300 Message-ID: <20090523214753.GA17590@amt.cnet> References: <4A09E620.3040300@xs4all.nl> <4A09F62A.8010203@xs4all.nl> <20090515144923.GA6304@amt.cnet> <4A0E7B81.6070203@xs4all.nl> <20090516131046.GB3153@amt.cnet> <4A152B7C.4080401@xs4all.nl> <4A152E9B.3060500@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org To: Hans de Bruin Return-path: Received: from mx2.redhat.com ([66.187.237.31]:43608 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753531AbZEWVsq (ORCPT ); Sat, 23 May 2009 17:48:46 -0400 Content-Disposition: inline In-Reply-To: <4A152E9B.3060500@xs4all.nl> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, May 21, 2009 at 12:36:11PM +0200, Hans de Bruin wrote: > Hans de Bruin wrote: >> Marcelo Tosatti wrote: >>> On Sat, May 16, 2009 at 10:38:25AM +0200, Hans de Bruin wrote: >>>> I ran memtest for 11 hours and it completed 4.7 passes with no problems. >>>> But then memtest is about cpu and memmory interaction. If the >>>> problem is disk related there is also disk/chipset/dma and memmory >>>> interaction. I could degrade my system by turning dma on disk io >>>> off, or i could have a closer look at kvm-autotest. >>> >>> Hans, >>> >>> It would be helpful if you can capture a few more KVM oopses, then. >>> >> >> >> v2.6.30-rc6-144-g5805977 >> kvm-86-122-ge2478f5 >> kvm from kernel >> simultaneously booting two w2k8. >> One vm dies: > > another one. This time the vm where booted sequentialy: > > [ 253.268993] kvm: 2907: cpu0 unimplemented perfctr wrmsr: 0xc0010003 > data 0x0 > [ 475.036542] rmap_remove: ffff8800cdb913b0 10 0->BUG ^^^ So 0x10 is 1 bit different from 0x00, which would be the no present entry for AMD. Usually an indication of hardware problems. Perhaps you want to try the test Lucas mentioned.