Hi Markus, This may be due to the configuration NFS client of the VMware hosts not being tuned. This article [1] may help with this issue.
Also, could it be that the VMware VM Images are bigger than the KVM ones? What sizes are we talking about? I also would like to point out that, to achieve the best performance (transfer-wise) for VMware based infrastructure, we recommend the use of VMFS partitions managed by the OpenNebula VMFS drivers [2]. Best regards, -Tino [1] http://www.vmware.com/files/pdf/techpaper/VMware-NFS-BestPractices-WP-EN.pdf [2] http://opennebula.org/documentation:rel3.8:vmware_ds#scenario_3pure_vmfs -- Constantino Vázquez Blanco, PhD, MSc | dsa-research.org/tinova Virtualization Technology Engineer / Researcher OpenNebula - The Open-Source Solution for Data Center Virtualization www.OpenNebula.org | @tinova79 | @OpenNebula On Tue, Jan 15, 2013 at 8:27 PM, Markus <[email protected]> wrote: > Hello, > I'm working with a small OpenNebula infrastructure with 2 KVM and 1 VMWare > host. All datastores are realized as a NFS share, located on the frontend > machine. > > When creating a new virtual machine, I experience the following behavior: > The copy and deployment process of a VM to an KVM node lasts only about 2 > minutes, but a deployment to the VMware node lasts up to 6 minutes. Is there > an explanation for this big difference? > All resources are working in the same local network. The datastore for KVM > images uses standard filessystem as datastore manager and the one for VMware > uses VMware datastore manager. > > Looking forward to some explanations. > > Thanks, > Markus > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
