Re: responding to buttonpress ACPI event sent by KVM/Qemu (same behavior in v5.2)

2014-02-10 Thread Robert Urban

On 02/04/2014 01:49 AM, Robert Urban wrote:
 On 02/03/2014 10:12 PM, Mike Larkin wrote:
 I'd run with acpi debug enabled, try to see if we are dropping an event.
 On a 5.4 test system I compiled a new generic MP kernel with option 
 ACPI_DEBUG
 and booted it. I set up a serial console.

 During boot there is a lot a ACPI debug output. I can make it available if
 anyone would like to see it.

 I then ran virsh shutdown guest. The guest froze without writing a single
 character to the console.

I found this description in a RedHat bugzilla entry:

 Gleb Natapov 2009-12-23 10:37:44 EST

 I posted patch to provide correct PCI irq routing info in mptable to kvm
 mailing list. It works for all devices except for SCI interrupt. BIOS
 programs SCI interrupt to be 9 as spec requires, but OpenBSD thinks that
 it is smarter and moves it to interrupts 10. Qemu will still send it on
 vector 9 and OpenBSD will enter the same infinity recursion. This can
 be triggered by issuing system_powerdown on qemu monitor.

the entry: https://bugzilla.redhat.com/show_bug.cgi?id=508801#c34

It sounds plausible.

There is a discussion about this on the KVM list:

http://www.spinics.net/lists/kvm/msg51563.html

I would be grateful if someone could have a look at this. I can make a OpenBSD
VM guest available.

Rob Urban



Re: responding to buttonpress ACPI event sent by KVM/Qemu (same behavior in v5.2)

2014-02-03 Thread Robert Urban

On 02/03/2014 10:12 PM, Mike Larkin wrote:
 I'd run with acpi debug enabled, try to see if we are dropping an event.
On a 5.4 test system I compiled a new generic MP kernel with option ACPI_DEBUG
and booted it. I set up a serial console.

During boot there is a lot a ACPI debug output. I can make it available if
anyone would like to see it.

I then ran virsh shutdown guest. The guest froze without writing a single
character to the console.

Rob Urban