Qemu Pegasos II interrupts issue

Try using AmigaOne XE or Sam460 emulation instead, IIRC the Pegasos2, emulation as well as real hardware, uses the same IRQ for nearly all hardware, for example the same IRQ is used for all PCI slots and maybe even for onboard devices like VIA PATA and USB, but next to no AmigaOS 4.x driver supports such shared IRQs.

Also in my understanding if multiple devices share an interrupt the interrupt handler should check each possible source and not ack the interrupt if none of the sources have active interrupt to avoid spurious interrupts.

Did you get any device failure during that time? For example, the ethernet suddenly stops working. What we're looking for is a change in IRQ behaviour when something goes wrong...

I don't know if this could be an issue with emulation or a bug in AmigaOS.

If you can reproduce the same with amigaone then it's more likely to be an issue in QEMU. If only happens on pegasos2 then it may be related to shared interrupts which may not be handled well in AmigaOS according to joerg so it could be a bug in AmigaOS that may need to be fixed to improve this.

Between 8.2 and 9.0 there were no changes to irq handling on pegasos2 and amigaone so probably it's the same with 8.2.1 but using the latest QEMU version may help to make sure you don't debug something that was already fixed.

I can't tell from the logs what could this be, I don't know much about PIC or it's emulation in QEMU, ...

Could this be something related to not handling spurious interrupts correctly in AmigaOS? I mean something like described here: https://forum.osdev.org/viewtopic.php?f=1&t=32722 Also in my understanding if multiple devices share an interrupt the interrupt handler should check each possible source and not ack the interrupt if none of the sources have active interrupt to avoid spurious interrupts.

But I can reproduce network failures and record the recording if that can be helpful. But even that probably won't help, as only the network is affected and everything else (sound/graphics etc.) will continue to work after the network has lost the connection.

I'm not convinced that Joerg is correct. After all, real Pegasos-II also shares the same interrupt between multiple devices. If shared interrupts were a problem, then we should see people with real Pegasos-IIs complaining about it.

Would require that there are people using AmigaOS 4.1 on a real Peagaos2

But even if all HW drivers would work correctly: What happens if there is an interrupt from 2 different devices at the same time?
With (nearly) every device using a different IRQ, like on the AmigaOne SE/XE/µA1, it's no problem: The interrupt handler functions are in different AmigaOS interrupt lists, one per IRQ number (IIRC the AmigaOS interrupt numbers/lists are ISA/PCI IRQ numbers +16 or +32).
But on the Pegasos2 I guess the interrupt handler of the first driver in the single interrupt list handles the interrupt and returns TRUE, which means no other interrupt handler function in the list gets called.
To make it work with shared IRQs like on the Pegasos2 the interrupt handler of all drivers may always have to return FALSE, even if it was an interrupt for their hardware they handled, to make sure the interrupt handler functions of other devices in the same interrupt list get called as well.

Would require that there are people using AmigaOS 4.1 on a real Peagaos2

One of the Friedens had a Pegasos2 for porting AmigaOS 4.x to it and probably Stéphane (peg2ide.device), but IIRC there was no single OS4 beta tester who had one as well.
I guess there are currently 1-5 users using AmigaOS 4.1 on a real Pegasos2 (kas1e has one) and about 20-30 using it with a QEmu emulated Pegasos2.