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

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

2014-02-03 Thread Robert Urban 
this is a (somewhat late) follow-up on the ACPI buttonpress event problem...
This was on misc@, but tech@ seems more appropriate.

On Sat, 24 Nov 2012 19:38:00 Tomas Bodzar wrote:

> On Sat, Nov 24, 2012 at 7:08 PM, IMAP List Administration  
> wrote:
> > Hello,
> >
> > some of you may remember a posting of mine here from March, 2012, in which I
> > mentioned that the ACPI buttonpress event is not being correctly transmitted
> > form a debian 6 host to an OpenBSD v5.1 guest.
> > 
> > In the meantime I've installed a OBSD v5.2 system which exhibits exactly the
> > same behavior -- the guest hangs (freezes) instantly and totally.
> > 
> > I've seen similar posts in the past which yielded replies mostly to the 
> > effect
> > of "OpenBSD's implementation is clean, Linux must be the bad guy".
> > 
> > I'm not interested in assigning blame, or seeing it assigned. I'd simply 
> > like to
> > see the problem solved, somehow.
> > 
> > Would a developer be willing to have a look, if I set up a v5.2 sandbox on 
> > the
> > debian host?
> 
> I think that for start devs will be missing what type of
> virtualization you're using on Debian, then it will be fine to see
> complete dmesg from OpenBSD guest 5.2 and as well latest snapshot.

The problem persists in 5.4 and the latest 5.5 snapshot. Below you will find 
the dmesg output for both versions.

The host is running Debian 6.0.8 (64bit). I'm using libvirt and KVM/Qemu for 
the virtualization:

QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5), Copyright (c) 
2003-2008 Fabrice Bellard

If more information is necessary, or if someone would like access to a test-VM, 
please get in touch.

cheers,

Rob Urban


-- dmesg from OpenBSD 5.4 --
OpenBSD 5.4 (GENERIC.MP) #0: Mon Jan 20 19:07:21 MET 2014
r...@dna54.y42.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3204427776 (3055MB)
avail mem = 3111464960 (2967MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xbec0 (11 entries)
bios0: vendor Bochs version "Bochs" date 01/01/2007
bios0: Bochs Bochs
acpi0 at bios0: rev 0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC HPET
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
acpihpet0 at acpi0: 1 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
mpbios0 at bios0: Intel MP Specification 1.4
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: QEMU Virtual CPU version 0.12.5, 3411.92 MHz
cpu0:
FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,POPCNT,NXE,LONG,LAHF,PERF
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line
16-way L2 cache
cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: smt 0, core 0, package 0
cpu0: apic clock running at 1000MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: QEMU Virtual CPU version 0.12.5, 3411.60 MHz
cpu1:
FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,POPCNT,NXE,LONG,LAHF,PERF
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line
16-way L2 cache
cpu1: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu1: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu1: smt 0, core 0, package 1
mpbios0: bus 0 is type PCI
mpbios0: bus 1 is type ISA
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
pciide0: channel 0 disabled (no drives)
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0:  ATAPI 5/cdrom removable
cd0(pciide0:1:0): using PIO mode 0
uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 2 int 11
piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 2 int 9
iic0 at piixpm0
iic0: addr 0x4c 48=00 words 00= 01= 02= 03= 04= 05=
06= 07=
iic0: addr 0x4e 48=00 words 00= 01= 02= 03= 04= 05=
06= 07=
vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00: Virtio
Network Device
vio0 at virtio0: address 52:54:00:d5:62:00
virtio0: apic 2 int 11
virtio1 at pci0 dev 4 function 0 "Qumranet Virtio Storage" rev 0x00: Virtio
Block Device
vioblk0 at virtio1
scsibus1 at vioblk0: 2 targets
sd0 at scsibus1 targ 0 lun 0:  SCSI3 0/direct fixed
sd0: 225280MB, 512 bytes/sector, 461373440 sectors
virtio1: apic 2 int 11
virti