Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#60940 - [qemu] consider patching qemu serial device for console kernel errors

Attached to Project: Arch Linux
Opened by Michael Taboada (lilmike) - Friday, 30 November 2018, 09:21 GMT
Last edited by David Runge (dvzrv) - Monday, 02 May 2022, 15:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Anatol Pomozov (anatolik)
David Runge (dvzrv)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No



When using qemu and having the guest kernel output messages to the console, you will get errors like this when using the serial console:

[108383.737511] serial8250: too much work for irq4

This is apparently because the serial emulation is sending data impossibly fast, so the kernel thinks it's a broken serial device (more info here:

Please consider patching qemu with the patch found here:

Additional info:
* package version(s) 3.0.0-4

Steps to reproduce:

1. Attach a serial device to a qemu/kvm vm, and make sure kernel is set to send messages error or better.
2. Connect using the serial console (virsh console <vm name>, for example).
This task depends upon

Closed by  David Runge (dvzrv)
Monday, 02 May 2022, 15:59 GMT
Reason for closing:  Won't implement
Additional comments about closing:  If this has not been fixed upstream, it will not be fixed. Applying untested patches from over a decade ago is not feasible.
Comment by loqs (loqs) - Friday, 30 November 2018, 20:00 GMT
Were you able to apply the referenced patch successfully and did it resolve the issue on your system?
Comment by Anatol Pomozov (anatolik) - Tuesday, 10 December 2019, 13:55 GMT
qemu version currently at the repo is 4.1.1. Serial driver moved to hw/char/serial.c for example. Could you please check the latest version of QEMU as well?

But this issue for upstream really. Please report this issue to QEMU maillist and share link to he discussion with us.