Skip to content

chore(ci): update qemu to 10.2.2#2390

Draft
nevermarine wants to merge 3 commits into
mainfrom
chore/ci/update-qemu-to-10.2.2
Draft

chore(ci): update qemu to 10.2.2#2390
nevermarine wants to merge 3 commits into
mainfrom
chore/ci/update-qemu-to-10.2.2

Conversation

@nevermarine
Copy link
Copy Markdown
Collaborator

Description

Update QEMU to 10.2.2 and keep the QEMU patch set aligned with that version by rebasing the no-bootable-device QMP patch and restoring the Nehalem HT feature patch.

Why do we need it, and what problem does it solve?

The repository still uses QEMU 9.2.0 while the QEMU-related patches need to be aligned with newer upstream sources. This PR updates the QEMU version to 10.2.2, fixes the 002-no-bootable-qmp.patch context for the new source tree, and restores 003-revert-nehalem-ht-feature.patch that was removed in commit 811e762b736aede0212f6ae5795d8dff5b8d2d81.

What is the expected result?

  1. Build the QEMU image with QEMU v10.2.2 sources.
  2. Verify 002-no-bootable-qmp.patch applies successfully during the build.
  3. Verify 003-revert-nehalem-ht-feature.patch is present in the patch set.
  4. Confirm the QEMU source tree is patched successfully and the image build proceeds without the previous patch-apply failure.

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: ci
type: chore
summary: "Update QEMU to 10.2.2 and align QEMU patches with the new source version."
impact_level: low

Signed-off-by: Maksim Fedotov <maksim.fedotov@flant.com>
Signed-off-by: Maksim Fedotov <maksim.fedotov@flant.com>
@nevermarine nevermarine marked this pull request as draft May 21, 2026 15:05
Signed-off-by: Maksim Fedotov <maksim.fedotov@flant.com>
@nevermarine nevermarine added this to the v1.9.0 milestone May 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant