10GB xfer speed

olivierlambert

Hi,

VMware import speed seems pretty normal, we have to make a lot of conversions on the fly Adding @florent in the loop

florent

@olivierlambert yes, the direct import process is quite slow. In our lab, it is also between 80-100Mbps per disk , it seems to be a limit of the vmware api we use here. Maybe you can transfer multiple VM in parallel to reduce the total migration time, but be careful to not overload the vmware cluster with too many queries

In some case, it can be faster to export the VM as an ova , copy it, and import it on XO 's side.

planedrop

Also wanted to chime in here that I was seeing about the same speeds when doing some ESXi importing to XCP-ng as well, seems pretty normal to me like @olivierlambert and @florent have already mentioned.

florent

BTW if any vmware wizard know a faster way to extract the data, we are interested
(nice to have : it doesn't require us to sacrifice any living being to an other plane entity )

bughatti

So I have been doing some testing. A question i am curious about, when you do the import from VMware, it just copies in the .vmdk, no conversions it seems. The file seems to have a lapel piece added in front of the .vmdk with [ESXI} Is this flag a manual piece that can be added through cli in some way?

How I have set things up is I have a truenas scale with an iscsi 10gb network. I added a second nic to xoa and put it on the same iscsi network and selected that interface as the main interface. I have the iscsi network added to all the xcp-ng hosts and mapped a nfs share over that 10gb network as a storage device. I then went in and selected the iscsi 10gb network in my vsphere environment and added management to each vmkernal port. I have a server 2019 veeam box on the same iscsi 10gb network i use to access xoa gui and also access each esxi host directly. I have the truenas nfs share mapped in xcp-ng to all hosts and also to one esxi node for testing. In vsphere, i migrated a test vm from its main vsan to the truenas nfs share. I then went in to truenas cli and validated i could see that folder structure with all files in it. What I dont see is the folder and files when rescanning the nfs share in xoa, so i am assuming when an import is done in xoa, it flags the files in a way that xoa can see them.

The speed is there, I am getting 1.2gb write speeds on my truenas iscsi zfs mount.

florent

@bughatti the vmdk can be, in fact, multiples files ( the base and a chain of delta between each snapshot)
the formats are : raw for the -flat.vmdk, vmdk cowd for the delat before esxi 6.5, and sesparse for 6.5 +
There are a lot of difference between this and the vhd format used by xen , and the translation is done without using any additional storage

If you can afford to shut down the VM and have enough free storage on disk, you can export the vmdk from your vmware platform, convert them to vhd with qemu-img convert and then load them Xen orchestra or xo-cli . That will be faster, but will need more resource and more manipulation on your end

bughatti

@florent So I tried and converted a vmdk to a vhdx and dumped it in the nfs share, i rescanned sr in xoa and xcp-ng center

I used veeam to export it out as a vhdx

no luck

olivierlambert

You need 2 conditions to do something like this:

only VHD format is supported (not VHDX, which is different)
the file MUST have the format <uuid>.vhd and be placed inside the SR folder (no sub-folders)

bughatti

@olivierlambert SO a couple things I am confused about.

Can no folders exist in the nfs datastore at all for it to read .vhd files because I just created a brand new nfs datastore on truenas scale and when I attached it to xoa, it create a folder called
ee832e6c-6974-f568-c236-9274307c40f1 in it.

Second, does the .vhd need to actually have a number.vhd like you stated uuid.vhd or can it be a name.vhd.

CasaOS_Disk_CasaOS.vhd
CasaOS_Disk_CasaOS_1.vhd

I currently have the 2 vhd's above in the sr and neither xcp-ng center nor xoa see them

olivierlambert

That's exactly what I said When you create a SR into an NFS path, it will create a new folder with a unique ID (UUID).

Then, all vhd files must be there "flat" (no subfolder). Also, the only format working is <uuid>.vhd, nothing else.

You can generate an UUID pretty easily with uuidgen.