From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin O'Connor Subject: Re: [Qemu-devel] E5-2620v2 - emulation stop error Date: Wed, 25 Mar 2015 16:54:39 -0400 Message-ID: <20150325205439.GA21667@morn.localdomain> References: <20150311184531.GA11423@morn.localdomain> <20150311191928.GA14695@morn.localdomain> <20150311193337.GA13162@work-vm> <20150311195920.GR2334@work-vm> <20150312095902.GC2330@work-vm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Dr. David Alan Gilbert" , Bandan Das , Paolo Bonzini , Gerd Hoffmann , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" To: Andrey Korolyov Return-path: Received: from mail-qg0-f41.google.com ([209.85.192.41]:36329 "EHLO mail-qg0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751342AbbCYUyn (ORCPT ); Wed, 25 Mar 2015 16:54:43 -0400 Received: by qgf60 with SMTP id 60so49435443qgf.3 for ; Wed, 25 Mar 2015 13:54:42 -0700 (PDT) Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Mar 25, 2015 at 11:43:31PM +0300, Andrey Korolyov wrote: > On Mon, Mar 16, 2015 at 10:17 PM, Andrey Korolyov wrote: > > For now, it looks like bug have a mixed Murphy-Heisenberg nature, as > > it appearance is very rare (compared to the number of actual launches) > > and most probably bounded to the physical characteristics of my > > production nodes. As soon as I reach any reproducible path for a > > regular workstation environment, I`ll let everyone know. Also I am > > starting to think that issue can belong to the particular motherboard > > firmware revision, despite fact that the CPU microcode is the same > > everywhere. > > > Hello everyone, I`ve managed to reproduce this issue > *deterministically* with latest seabios with smp fix and 3.18.3. The > error occuring just *once* per vm until hypervisor reboots, at least > in my setup, this is definitely crazy... > > - launch two VMs (Centos 7 in my case), > - wait a little while they are booting, > - attach serial console (I am using virsh list for this exact purpose), > - issue acpi reboot or reset, does not matter, > - VM always hangs at boot, most times with sgabios initialization > string printed out [1], but sometimes it hangs a bit later [2], > - no matter how many times I try to relaunch the QEMU afterwards, the > issue does not appear on VM which experienced problem once; > - trace and sample args can be seen in [3] and [4] respectively. Can you add something like: -chardev file,path=seabioslog.`date +%s`,id=seabios -device isa-debugcon,iobase=0x402,chardev=seabios to the qemu command line and forward the resulting log from both a succesful boot and a failed one? -Kevin