From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [Qemu-devel] E5-2620v2 - emulation stop error Date: Wed, 11 Mar 2015 18:41:07 +0100 Message-ID: <55007E33.7080107@redhat.com> References: <54FF337A.1010202@redhat.com> <54FF4541.9080608@redhat.com> <20150310202958.GR2338@work-vm> <20150311134556.GH2334@work-vm> <20150311154220.GA26463@morn.localdomain> <20150311155306.GK2334@work-vm> <20150311163739.GA29522@morn.localdomain> <20150311165203.GL2334@work-vm> <20150311173738.GD29522@morn.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Bandan Das , kraxel@redhat.com, Andrey Korolyov , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" To: "Kevin O'Connor" , "Dr. David Alan Gilbert" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:60587 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751349AbbCKRlU (ORCPT ); Wed, 11 Mar 2015 13:41:20 -0400 In-Reply-To: <20150311173738.GD29522@morn.localdomain> Sender: kvm-owner@vger.kernel.org List-ID: On 11/03/2015 18:37, Kevin O'Connor wrote: > > I'm going to check the assembly for a compiler error, but is it > > possible QEMU is returning incorrect data in cmos index 0x5f? > > I checked the SeaBIOS assembler and it looks sane. So, I think the > question is, why is QEMU sometimes returning a 0 instead of 127 from > cmos 0x5f. Dave, can you get a KVM trace (trace-cmd record -e kvm/* qemu-system-x86_64 ...) and send it to me privately? Paolo