Skip to content

fix(core): better handling VMs with osType=Windows#2345

Draft
diafour wants to merge 2 commits into
mainfrom
fix/core/tsc-labels-unschedulable
Draft

fix(core): better handling VMs with osType=Windows#2345
diafour wants to merge 2 commits into
mainfrom
fix/core/tsc-labels-unschedulable

Conversation

@diafour
Copy link
Copy Markdown
Member

@diafour diafour commented May 13, 2026

Description

  1. More stable TSC labels to handle VMs with reenlightenment feature (mostly Windows guests).

See: deckhouse/3p-kubevirt#109

  1. Prevent stale labels with empty values on Nodes.

See: deckhouse/kube-api-rewriter#7

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

CPU frequency drifts on Nodes may lead to "Unschedulable" and non-migratable VMs.

What is the expected result?

VMs with Windows guests starts and migrates.

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: core
type: fix
summary: "Better handling Windows guests: start and migration should work in clusters with frequent CPU frequencies drifts"

1) More stable TSC labels to handle VMs with reenlightenment feature (mostly Windows guests).

See: deckhouse/3p-kubevirt#109

2) Prevent stale labels with empty values on Nodes.

See: deckhouse/kube-api-rewriter#7
Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
@diafour diafour added this to the v1.9.0 milestone May 13, 2026
@diafour diafour changed the title fix(core): better handling osType: Windows VMs fix(core): better handling VMs with osType=Windows May 13, 2026
Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
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