Skip to content
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

Restrict Windows Conversion to only use virt-v2v, refuse to fallback #1

Closed
3 tasks done
onenhansen opened this issue Apr 8, 2024 · 0 comments
Closed
3 tasks done
Assignees
Labels
enhancement New feature or request

Comments

@onenhansen
Copy link
Contributor

onenhansen commented Apr 8, 2024

Windows requires many changes internally for conversion to properly happen to be able to run on KVM properly. When converting Windows, the only option should be the virt-v2v conversion, and should present a large warning that --fallback is not compatible with Windows.

  • Code written/tested
  • Code committed
  • Documentation/README
@onenhansen onenhansen added the enhancement New feature or request label Apr 8, 2024
@onenhansen onenhansen self-assigned this Apr 8, 2024
onenhansen added a commit that referenced this issue Apr 8, 2024
B #2: context inject now uses virt-customize

Signed-off-by: Neal Hansen <nhansen@opennebula.io>
onenhansen added a commit that referenced this issue Apr 8, 2024
Signed-off-by: Neal Hansen <nhansen@opennebula.io>
onenhansen pushed a commit that referenced this issue May 22, 2024
Feature add for migrations for windows and Linux
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant