Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
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!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
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
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
|
DetailsDescription:
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: https://unix.stackexchange.com/questions/387600/understanding-serial8250-too-much-work-for-irq4-kernel-message). Please consider patching qemu with the patch found here: https://lkml.org/lkml/2008/2/7/485 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.
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.
But this issue for upstream really. Please report this issue to QEMU maillist and share link to he discussion with us.