-
Notifications
You must be signed in to change notification settings - Fork 473
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
Support vCenter managed disks in DS migration #2875
Comments
Semedi
pushed a commit
to Semedi/one
that referenced
this issue
Feb 15, 2019
Semedi
pushed a commit
to Semedi/one
that referenced
this issue
Feb 15, 2019
Semedi
pushed a commit
that referenced
this issue
Feb 18, 2019
Semedi
pushed a commit
that referenced
this issue
Feb 18, 2019
Semedi
pushed a commit
that referenced
this issue
Feb 18, 2019
Semedi
pushed a commit
that referenced
this issue
Feb 18, 2019
Semedi
pushed a commit
that referenced
this issue
Feb 18, 2019
Semedi
pushed a commit
that referenced
this issue
Feb 18, 2019
actually done in 5.8 |
rsmontero
pushed a commit
that referenced
this issue
Jan 3, 2024
rsmontero
pushed a commit
that referenced
this issue
Mar 11, 2024
(cherry picked from commit 9177157)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
Currently only VMs with managed disks can be migrated
Use case
Support DS migration in all possible VMs
Interface Changes
None
Additional Context
Need a change in the reference of the VM disks, path are no longer valid since managed disks are not originally in the VM folder, but after the migration they are since vCenter performs the moving of the disks.
An alternative is to update the VM representation after the migration.
Progress Status
The text was updated successfully, but these errors were encountered: