If you are going from VMware to CloudStack Managed VMware, this is something I have done quite a bit. I even built a tool to do this: https://github.com/swill/migrate2cs
This is not a polished product. Well, it is pretty polished once you get it setup, but the setup is a bit complicated to get started. If you would like to use it, let me know and I will do what I can to get you setup. *Will Stevens* CTO <https://goo.gl/NYZ8KK> On Thu, Jul 13, 2017 at 9:52 AM, Shreya Nair <shreya.n...@opcito.com> wrote: > Hello, > > *An update to the migration task:* > > We have installed Cloudstack onto a vm on VMware to work around the > cross-hypervisor migration issue. Now the underlying hypervisor would be > the ESXi server for both setups (VMware and Cloudstack). > > Currently, we create the corresponding equivalent infrastructure on > CloudStack wrt vmware setup. We create a zone, pod, cluster and host set > up with the underlying network infrastructure. However, while setting up > the storage (Primary storage at cluster-wide scope and Secondary storage at > zone-wide) the documentation mentions the following warnings: > > > - *Primary storage warning:* > - When using preallocated storage for primary storage, be sure there > is nothing on the storage (ex. you have an empty SAN volume or > an empty NFS > share). Adding the storage to CloudStack will destroy any existing > data. > - *Secondary storage warning:* > - Ensure that nothing is stored on the server. Adding the server to > CloudStack will destroy any existing data. > > > We have obtained the mysql dump of the datastore of the source VM on > VMware. The datastore, as you may be aware, is a logical container that > holds virtual machine files and other files necessary for VM operations. As > such, it may be logically mapped to the Secondary storage setup in the > CloudStack infrastructure. > > Would it be possible to use the mysql dump from source to update the > Secondary storage? > > Thanks & Regards, > > Shreya > > On Fri, Jul 7, 2017 at 4:04 PM, Paul Angus <paul.an...@shapeblue.com> > wrote: > > > Maybe you should try qemu-img instead. > > > > > > Kind regards, > > > > Paul Angus > > > > > > paul.an...@shapeblue.com > > www.shapeblue.com > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > > > From: Shreya Nair [mailto:shreya.n...@opcito.com] > > Sent: 07 July 2017 11:30 > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org > > Cc: Vinay Patil <vinay.pa...@opcito.com>; Siddheshwar More < > > siddheshwar.m...@opcito.com> > > Subject: Re: DISCUSS : Vmware to Cloudstack migration support > > > > Hi Paul, > > We explored the XenConvert solution. The XenConvert utility has been > > retired from XenServer 6.2 and upward. So the only solution would be > using > > an old copy or trial version of Xen Conversion Manager. > > > > Instead of the qemu-img utility, we used the VirtualBox VBoxManage.exe to > > support conversion of *.VMDK file to VHD. This VHD file was used to > create > > a CS template and create an instance. However, the VM was unable to mount > > the drives as it was unable to find xvdXX partitions > > > > > > I get the following error on CS instance on boot: > > [Inline image 2] > > > > and the logs shows us this: > > > > You might have to change the root from /dev/hd[a-d] to /dev/xvd[a-d] > > > > > > > > However, on using lsblk command on the source vmware instance, we > realized > > that the partitions on SCSI storage devices (Used by vmware) are named as > > /dev/sdXX while Xen supports /dev/xvdXX. > > [Inline image 1] > > > > Note: VMware tools has been removed from VM prior to migration > > > > > > > > Thanks & Regards, > > > > Shreya > > > > On Thu, Jul 6, 2017 at 12:17 AM, Paul Angus <paul.an...@shapeblue.com< > > mailto:paul.an...@shapeblue.com>> wrote: > > There used to be a XenConvert utility that you do that conversion for > > you. I'm not sure that its about anymore, but a bit of googling might > dig > > up a copy. > > > > Alternatively there are linux and Windows versions of qemu-img convert , > > which usually does a pretty good job of disk image conversions > > > > Otherwise you could use a P2V backup/recovery tool with an agent that > runs > > inside your VMs > > > > > > > > Kind regards, > > > > Paul Angus > > > > paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com> > > www.shapeblue.com<http://www.shapeblue.com> > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > > > > > -----Original Message----- > > From: Shreya Nair [mailto:shreya.n...@opcito.com<mailto: > > shreya.n...@opcito.com>] > > Sent: 05 July 2017 09:22 > > To: us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org> > > Subject: Re: DISCUSS : Vmware to Cloudstack migration support > > > > Hi Oliver, > > > > We are trying to migrate the vSphere environment to cloudstack (based on > > XenServer) due to some internal product dependency which can be addressed > > by the CloudStack environment. > > > > > > Thanks & Regards, > > > > Shreya > > > > On Tue, Jul 4, 2017 at 10:27 PM, Oliver Dzombic <i...@ip-interactive.de< > > mailto:i...@ip-interactive.de>> > > wrote: > > > > > Hi, > > > > > > just our of intrest: > > > > > > Why do you want to go away from vmware ? > > > > > > And why do you prefere xen and not kvm ( which is as you already > > > experienced much more tricky compared to kvm ) ? > > > > > > > > > -- > > > Mit freundlichen Gruessen / Best regards > > > > > > Oliver Dzombic > > > IP-Interactive > > > > > > mailto:i...@ip-interactive.de<mailto:i...@ip-interactive.de> > > > > > > Anschrift: > > > > > > IP Interactive UG ( haftungsbeschraenkt ) Zum Sonnenberg 1-3 > > > 63571 Gelnhausen > > > > > > HRB 93402 beim Amtsgericht Hanau > > > Geschäftsführung: Oliver Dzombic > > > > > > Steuer Nr.: 35 236 3622 1 > > > UST ID: DE274086107 > > > > > > > > > Am 04.07.2017 um 13:22 schrieb Shreya Nair: > > > > Hello, > > > > > > > > My team is working on a Vmware to Cloudstack migration task. The > > > CloudStack > > > > environment is set up on the Xenserver hypervisor. > > > > > > > > We are able to export a VM on vsphere to OVF template which also > > > > provides the OVF, VMDK disk image(s) and MF file for the particular > VM. > > > > In order to create a CloudStack Template from these files, it can be > > > > done by 2 methods, namely, template creation from VHD(as the > > > > underlying hypervisor is XenServer) or template creation from ISO. > > > > > > > > VHD Template creation: > > > > - The VMDK file (Obtained after export OVF operation of the VM) is > > > > converted to VHD format with VBoxManage.exe tool that is available > > > > with VirtualBox. > > > > - The VHD file can be used to create a CloudStack template and > > > > instantiate a VM. > > > > > > > > > > > > ISO Template creation: > > > > - The OVF file (Obtained after export OVF operation of the VM) is > > > imported > > > > to Citrix XenCenter. > > > > - XenCenter runs Operating system Fixup on the imported OVF file > > > > and creates a modified ISO file. > > > > - The modified ISO file can be used for creating a template and > > > > instantiate a VM > > > > > > > > However, the newly created VM has booting issues as it requires "You > > > might > > > > have to change the root from /dev/hd[a-d] to /dev/xvd[a-d]" > > > > Is there an alternate way or support to migrate a vSphere VM to > > > CloudStack? > > > > Or a method to change the partitioning on the hard disk from sd[a-d] > > > > to xvd[a-d] > > > > > > > > > > > > > > > > Thanks & Regards, > > > > > > > > Shreya > > > > > > > > > > > >
