Skip to content

Conversation

@orelmisan
Copy link
Member

@orelmisan orelmisan commented Oct 28, 2025

VEP Metadata

Tracking issue:

What this PR does

Special notes for your reviewer

@kubevirt-bot kubevirt-bot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. sig/network labels Oct 28, 2025
@kubevirt-bot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign xpivarc for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@orelmisan
Copy link
Member Author

/cc @Barakmor1

@orelmisan
Copy link
Member Author

@Barakmor1's kubevirt/kubevirt#16212 is a POC of the mechanism proposed here.

Comment on lines +98 to +106
1. The target virt-launcher process starts, creates a Unix domain socket, and begins listening for incoming connections.
2. As part of the migration, libvirt executes the hook script on the target pod, passing the original domain XML to the
script's stdin.
3. The hook script connects to the virt-launcher's Unix socket and passes the domain XML from its stdin to the socket.
4. The virt-launcher server receives the XML, parses it, scans for legacy configurations (like ordinal interface names),
and performs the necessary mutations.
5. virt-launcher sends the mutated domain XML back to the hook script over the same socket connection.
6. The hook script reads the mutated XML from the socket and writes it to its stdout.
7. Libvirt reads the stdout from the hook script and uses this final, modified XML to define the VM on the target.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@orelmisan Thanks for keeping me involved in this work.

This PR is inspired by the plan we discussed.
Additional details are described in the PR description.

@xpivarc
Copy link
Member

xpivarc commented Nov 26, 2025

/cc

@orelmisan
Copy link
Member Author

As discussed on yesterday's SIG compute call, this VEP will depend on #141.

@orelmisan orelmisan marked this pull request as draft November 27, 2025 12:04
@kubevirt-bot kubevirt-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. sig/compute sig/network size/L

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants