Ravello offers an import tool that enables organizations to easily upload their VMware and KVM VMs to Ravello’s platform in a variety of ways - directly from vCenter or vSphere, as an OVF, or by uploading disk files and images (ISOs, VMDKs, QCOWs).
As one may expect, the time taken to upload the VM by the import tool depends on -
We recently ran some tests using Ravello’s VM import tool to characterize the upload time taken based on the type of link. We emulated the WAN link using the popular tool - WANem - and uploaded a 78 MB ISO file for our tests.
As expected, the upload time was small for links with higher bandwidths (e.g. OC-9, FDDI etc.) and large for links with lower bandwidths (e.g. T-1, ADSL etc.). The following chart should give one a rough estimate of the time it would take to upload a similar sized VM based on the link available (note the logarithmic scale for the bandwidth axis).
Next, we looked into the impact of link characteristics on the upload time. Keeping the bandwidth constant at 10 Mbps (CAT-3), we uploaded the 78 MB ISO file for our tests at different levels of packet loss. As expected, the upload time increases with the increase in packet loss. At greater than 20% packet loss, the upload time increase exponentially - thanks to multiple re-transmissions. It is interesting to note that with packet losses less than 15%, the VM import tool is able to gracefully recover keeping the upload time fairly constant.
If you are facing challenges with Ravello Import Tool that cannot be explained by the bandwidth and link characteristics mentioned above, here are some things to look into -
Amazon’s S3 - home to the VMs in your VM library is sensitive to machine clock timestamps. If the system clock of the machine that is using the upload tool is not set accurately the upload will fail on 1% progress. To get around this issue, sync the system clock to pool.ntp.org
If your environment requires a proxy to be able to access the internet, you will need configure proxy’s IP in Ravello’s VM Import tool before you can upload. Instructions on how to setup proxy is available in Ravello’s knowledge base.
Ungraceful shutdowns, hibernation of the machine running VM Import tool in the middle of an upload has the potential to corrupt the tool database. This can lead to user being unable to login to the tool. To work around this issue, one needs to reset the tool by -
The VM Import Tool uploads in chunks. Until the first chunk is fully uploaded the progress bar shows 1%, and as more chunks are uploaded the progress bar gets updated. On slow links, the progress bar show 1% for a long time until the first chunk is uploaded - and then suddenly jump to a higher percentage. If you are concerned that VM Import is not uploading properly, take a peek into the logs to confirm that upload is in progress.
Feeling adventurous, and want to explore what is going on behind the scenes? Read on.
1. With your Ravello VM Import Tool running, type
http://127.0.0.1:8881/hello in your web-browser
2. Your browser should display the location where the log file for VM Import Tool is being stored
3. On Windows the default location is C:WindowsTemp.ravellostore.log and on Mac OSX the default location is /Users/<name>/.ravello/store.log
4. Open the store.log in Notepad (Windows) or Console (Mac). Following snippet indicates that upload has started
5. Following snippet indicates that upload has completed
If your upload issues persist, please reach out to Ravello Support team with a copy of your store.log, and we will be happy to help.