[SeaBIOS] system_powerdown not working for qemu-kvm 0.12.4?
avi at redhat.com
Tue Oct 12 09:33:42 CEST 2010
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 commit
>> > > >commit 5c99b6c984682ddb1d4543a7e27a1f4ca633e6a6
>> > > >Author: Kevin O'Connor<kevin at koconnor.net>
>> > > 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 kvm
>> > > implements but qemu does not)
>> > The only thing in commit 5c99b6c9 that could cause an issue is that it
>> > has the compiled acpi changes actually made in commit 29f4b912, but 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
> IRQ9OUT#, which indicates it's active low, though that isn't set down
> Qemu however emulates it as active high. Other guests work, which is
Aha! The piix4 specification updates says:
> • IRQ9OUT#/GPO29 should be labeled as IRQ9OUT/GPO29
So it looks like it should be active high, and seabios is wrong in
listing it as active low. Perhaps other OSes have quirks to force it to
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
More information about the SeaBIOS