-
Notifications
You must be signed in to change notification settings - Fork 24
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
Conversation
There was a problem hiding this 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.
c7b0ba3
to
19a0baf
Compare
|
||
* Removals: | ||
|
||
** Unnecessary or former hypervisor-specific files (for example, VMware tools, VirtualBox additions) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
** 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`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. |
There was a problem hiding this 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
19a0baf
to
186e531
Compare
Signed-off-by: RichardHoch <[email protected]>
c38c712
to
9b53394
Compare
@anarnold97 I made trhe changes you suggested. Please review this PR again. Thanks. |
There was a problem hiding this 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
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