From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: system_powerdown not working for qemu-kvm 0.12.4? Date: Tue, 12 Oct 2010 09:33:42 +0200 Message-ID: <4CB40F56.20402@redhat.com> References: <4BEFDC8D.70007@redhat.com> <4BF41051.2010608@redhat.com> <4C67C8D2.5000400@redhat.com> <4CB341E4.3060400@redhat.com> <4CB40515.2030809@redhat.com> <20101012071124.GA10190@morn.localdomain> <20101012071404.GA18974@redhat.com> <4CB40D87.6000405@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: "Kevin O'Connor" , Ruben Kerkhof , Teck Choon Giam , kvm@vger.kernel.org, seabios@seabios.org To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:9108 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754933Ab0JLHef (ORCPT ); Tue, 12 Oct 2010 03:34:35 -0400 In-Reply-To: <4CB40D87.6000405@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 10/12/2010 09:25 AM, Avi Kivity wrote: > On 10/12/2010 09:14 AM, Gleb Natapov wrote: >> On Tue, Oct 12, 2010 at 03:11:24AM -0400, Kevin O'Connor wrote: >> > On Tue, Oct 12, 2010 at 08:49:58AM +0200, Avi Kivity wrote: >> > > On 10/11/2010 07:53 PM, Ruben Kerkhof wrote: >> > > >5c99b6c984682ddb1d4543a7e27a1f4ca633e6a6 is the first bad commi= t >> > > >commit 5c99b6c984682ddb1d4543a7e27a1f4ca633e6a6 >> > > >Author: Kevin O'Connor >> > > Gleb, Kevin, any ideas? >> > > >> > > (summary: qemu-kvm doesn't acpi shutdown freebsd 8.1 with this >> > > commit; qemu.git does. May be due to interrupt polarity which kv= m >> > > implements but qemu does not) >> > >> > The only thing in commit 5c99b6c9 that could cause an issue is tha= t it >> > has the compiled acpi changes actually made in commit 29f4b912, bu= t I >> > don't see how that would be a problem to reboots: >> > >> It makes line 0 of device 1 to be active low instead of active high. > > Correctly, according to the documentation (the line is marked=20 > IRQ9OUT#, which indicates it's active low, though that isn't set down= =20 > elsewhere). > > Qemu however emulates it as active high. Other guests work, which is=20 > wierd. > Aha! The piix4 specification updates says: > > =95 IRQ9OUT#/GPO29 should be labeled as IRQ9OUT/GPO29 So it looks like it should be active high, and seabios is wrong in=20 listing it as active low. Perhaps other OSes have quirks to force it to= =20 active high. --=20 I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.