Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

Update README.md to add a known issue regarding storage vmotion of VM [SKIP CI] #1639

Merged
merged 2 commits into from
Aug 1, 2017
Merged

Update README.md to add a known issue regarding storage vmotion of VM [SKIP CI] #1639

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a686bb2
Update README.md to add a known issue regarding storage vmotion of VM.
lipingxue Jul 26, 2017
c11e980
Address comments from Sam and Govindan.
lipingxue Jul 27, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,6 +163,8 @@ logging config format for content details.
- Full volume name with format like "volume@datastore" cannot be specified in the compose file for stack deployment. [#1315](https://github.com/vmware/docker-volume-vsphere/issues/1315). It is a docker compose issue and a workaround has been provided in the issue.
- Specifying "Datastore Cluster" name during volume creation is not supported. Datastore clusters (as a part of Storage DRS) is a VC feature and not available on individual ESX. [#556](https://github.com/vmware/docker-volume-vsphere/issues/556)
- Volume creation using VFAT filesystem is not working currently. [#1327](https://github.com/vmware/docker-volume-vsphere/issues/1327)
- Volume is not shown when running ```docker volume ls``` and ```vmdkops_admin volume ls``` command after performing Storage vMotion of VM when volume is attached to VM. It is an expected behavior since Storage vMotion changes the location and name of attached vmdk files.
We only see this when trying to do Storage vMotion with volume attached. So avoid Storage vMotion when volume is attached. [#1618](https://github.com/vmware/docker-volume-vsphere/issues/1618)

## Contact us

Expand Down