I am curious, when you say you used VMware's Storage vMotion, do you mean the intent was to live migrate the storage underlying one of your VMs? I was not aware that CloudStack supported this.
I believe CloudStack supports the offline migration of VM disks, but it seems to me that, say, offline migrating a root disk wouldn't bring along the config and log files that also shared the same datastore with that root disk (perhaps it should, though). Maybe one of our VMware gurus can explain what is the expected behavior here. On Thu, Feb 12, 2015 at 5:24 PM, Star Guo <st...@ceph.me> wrote: > Does any one know about that ? > > Best Regards, > Star Guo > > -----邮件原件----- > 发件人: Star Guo [mailto:st...@ceph.me] > 发送时间: 2015年2月12日 9:24 > 收件人: us...@cloudstack.apache.org > 主题: About Instance Storage Live Migration on VMware > > Hi, All, > > > > My env is cloudstack 4.4.2 + VMware 5.5, and it works well. > > I deploy an instance and try to migrate the ROOT disk to another vmfs > primary storage. After that I find the ROOT disk is in new vmfs primary > storage but the .vmx , .vmxf and .log etc still in the origin vmfs primary > storage. > > If I want to migrate the instance (all of the files in the floder of the > instance) to new vmfs primary storage, May CloudStack 4.4.2 Support to do > this ? Thanks. > > > > Best Regards, > > Star Guo > > > > > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud <http://solidfire.com/solution/overview/?video=play>*™*
