Skip to content

Duplicate default persistent routes exist in VM after migration #85

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Hazanel
Copy link

@Hazanel Hazanel commented May 6, 2025

Clean up duplicate persistent routes from registry during boot sequence.

@rwmjones
Copy link
Member

rwmjones commented May 7, 2025

The commit message should start with a single line description of the change (not "MTV-2426"), followed by a blank line, followed by a longer descrition of the change. The commit message should also have at the end Fixes: https://issues.redhat.com/browse/RHEL-89939.

Note that \\ (double backslash) appears as a single backslash in the output script, so I hope that's what you intended. If you want a double backslash in the output you have to use \\\\.

Has this been tested? How should it be tested?

There's a strange extra merge commit added, unclear what that's for.

During the conversion of Windows virtual machines,
some persistent static routes were being duplicated in the Windows registry.
This change adds a cleanup step during the boot sequence to
remove redundant entries from the PersistentRoutes registry key,
ensuring that only unique static routes are retained and applied at boot time.

Fixes: https://issues.redhat.com/browse/RHEL-89939.
Signed-off-by: ehazan <[email protected]>
@Hazanel Hazanel force-pushed the remDupPersistentRoutes branch from 0017adb to 9f871a6 Compare May 7, 2025 09:02
@Hazanel Hazanel changed the title MTV-2426 | Duplicate default persistent routes exist in VM after migration Duplicate default persistent routes exist in VM after migration May 7, 2025
@Hazanel
Copy link
Author

Hazanel commented May 7, 2025

I hope it's better now.
About testing : we should migrate the vm and use the updated virt-v2v and see in the dest vm the routing table has no duplication.
Giving you the virt-v2v command line would help?

@rwmjones
Copy link
Member

rwmjones commented May 7, 2025

You should be able to test this yourself. After compiling virt-v2v (see https://github.com/libguestfs/virt-v2v/blob/master/README, do not install it), run virt-v2v on a Windows disk image using:

$ ./run virt-v2v -i disk windows.img -o local -os /var/tmp --mac 52:42:00:d0:cf:0e:network:mgmt

and boot up the output VM:

$ qemu-system-x86_64 -machine accel=kvm:tcg -cpu host -m 2048 -drive file=/var/tmp/windows-sda,format=raw,if=virtio

and check it does what you expect.

I don't think we have a conversion log on the original bug yet so I don't know what exact network options were used that caused the problem, so above --mac is just a guess.

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.

2 participants