-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Qemu-guest-agent is missing in QEMU aarch64 image #1593
Comments
Hi @sergey-cheperis and thanks for the report! Here's the fixing PR: flatcar/scripts#2490, I will discuss with Flatcar folks but there is a high chance to backport the fix on all channels (alpha, beta, stable and LTS). A CI job is running to build the image, would you be able to test the ARM64 image to see if it brings the EDIT: Here's the image if you want to try: https://bincache.flatcar-linux.net/images/arm64/9999.0.101+tormath1-guest-agent-arm/flatcar_production_qemu_uefi_secure_image.img |
Hi Mathieu, thanks a lot you for handling this so fast. I can confirm that in this image the issue is resolved. |
The issue has been solved and released, I am going to close this one. Thanks for opening this issue :) |
Description
Per https://www.flatcar.org/docs/latest/setup/customization/acpi/, images should include
qemu-guest-agent
which is enabled whenorg.qemu.guest_agent.0
virtio port is present. However, theflatcar_production_qemu_uefi_secure_image.img
image foraarch64
does not contain it.Impact
Guest automation depending on the guest agent does not work.
Environment and steps to reproduce
flatcar_production_qemu_uefi_secure_image.img
foraarch64
archictecture. The version being tested is 4081.2.0. Use the following qemu args to add the virtio port:ls -la /dev/virtio-ports/
shows theorg.qemu.guest_agent.0
port.which qemu-guest-agent
does not show anything, neither doespgrep qemu
.Expected behavior
A
qemu-guest-agent
executable exists and is started.The text was updated successfully, but these errors were encountered: