diff options
| author | Michal Privoznik <michal.privoznik@gmail.com> | 2024-11-06 21:27:22 +0100 |
|---|---|---|
| committer | Sam James <sam@gentoo.org> | 2025-08-26 16:25:32 +0100 |
| commit | 1d5cfbbf84ca69ab68caf979f2f3c03b037695c7 (patch) | |
| tree | 4647902b6fec019b63955dd703b075c3ec83c304 /dev-python/bpython/metadata.xml | |
| parent | 11d05ab1534e0c254a4f46252f2523d74054fc5a (diff) | |
| download | gentoo-1d5cfbbf84ca69ab68caf979f2f3c03b037695c7.tar.gz gentoo-1d5cfbbf84ca69ab68caf979f2f3c03b037695c7.tar.bz2 gentoo-1d5cfbbf84ca69ab68caf979f2f3c03b037695c7.zip | |
app-emulation/qemu-guest-agent: Check for VIRTIO_CONSOLE kernel config
To control guests from inside qemu-guest-agent is used. By
default, it listens on a virtio-serial device
(/dev/virtio-ports/org.qemu.guest_agent.0, see [1]) which is available iff
CONFIG_VIRTIO_CONSOLE kernel config is enabled. Due to a bug in
qemu-guest-agent where it daemonizes itself before opening the
device, init scripts are unable to tell whether startup was
successful. Check for the kernel config knob and hope that users
will notice it while emerging the package. There is a fix for the
bug [2] but it's contained in 10.0.0 release.
1: https://gitlab.com/qemu-project/qemu/-/blob/88f72048d2f5835a1b9eaba690c7861393aef283/qga/main.c#L46
2: https://gitlab.com/qemu-project/qemu/-/commit/c6f5dd7ac8ef62dcdec4cdeda1467c658161afff
Closes: https://bugs.gentoo.org/810628
Signed-off-by: Michal Privoznik <michal.privoznik@gmail.com>
Part-of: https://github.com/gentoo/gentoo/pull/43567
Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'dev-python/bpython/metadata.xml')
0 files changed, 0 insertions, 0 deletions