You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a follow-up to #1877, we should then allow adding additional disks to a container or VM as part of their migration. When doing so, those extra disks would first be transferred as custom volumes before the instance itself is transferred and the disks connected.
For containers, we'll only allow extra file system custom volumes (path).
For VMs, we'll support either file system or block (including qcow2 and vmdk as supported for the root volume).
What do you think would need to be added
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
What are you currently unable to do
As a follow-up to #1877, we should then allow adding additional disks to a container or VM as part of their migration. When doing so, those extra disks would first be transferred as custom volumes before the instance itself is transferred and the disks connected.
For containers, we'll only allow extra file system custom volumes (path).
For VMs, we'll support either file system or block (including qcow2 and vmdk as supported for the root volume).
What do you think would need to be added
No response
The text was updated successfully, but these errors were encountered: