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

MTV-1696: How MTV uses virt-v2v #615

Merged
merged 2 commits into from
Jan 30, 2025
Merged

Conversation

RichardHoch
Copy link
Collaborator

@RichardHoch RichardHoch commented Jan 12, 2025

MTV 2.8

Partly resolves https://issues.redhat.com/browse/MTV-1696 by adding a section discussing how MTV uses virt-v2v in migrations.

Preview: https://file.corp.redhat.com/rhoch/virt_v2v_mtv/html-single/#virt-v2v-mtv_mtv

Copy link
Contributor

@fabiand fabiand left a comment

Choose a reason for hiding this comment

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

This is good to go.

@RichardHoch RichardHoch force-pushed the virt_v2v_mtv branch 2 times, most recently from c7b0ba3 to 19a0baf Compare January 29, 2025 12:02

* Removals:

** Unnecessary or former hypervisor-specific files (for example, VMware tools, VirtualBox additions)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
** Unnecessary or former hypervisor-specific files (for example, VMware tools, VirtualBox additions)
** Unnecessary or former hypervisor-specific files, for example, VMware tools, VirtualBox additions.

[id="permissions-virt-v2v_{context}"]
== Permissions and virt-v2v

`virt-v2v` does not require permissions or access credentials of the guest operating system itself because `virt-v2v` is not run against a running VM, but only against the disks of a VM.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
`virt-v2v` does not require permissions or access credentials of the guest operating system itself because `virt-v2v` is not run against a running VM, but only against the disks of a VM.
`virt-v2v` does not require permissions or access credentials for the guest operating system itself because `virt-v2v` is not run against a running VM, but only against the disks of a VM.

Copy link
Collaborator

@anarnold97 anarnold97 left a comment

Choose a reason for hiding this comment

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

There are a number of changes that I would suggest

I much prefer using the AsciiDoc link macro, for searchability among other reasons

@RichardHoch
Copy link
Collaborator Author

@anarnold97 I made trhe changes you suggested. Please review this PR again. Thanks.

Copy link
Collaborator

@anarnold97 anarnold97 left a comment

Choose a reason for hiding this comment

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

One small change which i have force pushed

@anarnold97 anarnold97 merged commit e0925da into kubev2v:main Jan 30, 2025
1 check failed
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.

3 participants