OpenVZ on NFS Storage, container creation very slow

  • Thread starter Thread starter kappakairi
  • Start date Start date
K

kappakairi

Guest
I'm having an issue when creating a container with storage on my NFS storage in Proxmox. I have tried putting the template files in both local and the same NFS storage device, either way the container creation takes over 20-30 minutes. However, creating KVMs on this same NFS storage is quite fast and there isn't any reason the NFS drive should be this slow.

Also I was able to create OpenVZ containers on local storage and the creation speed is normal and is done in a couple of seconds.

Has anyone had any similar issues or know of the problem/possible solution?

Thanks in advance.
 
I went through similar issue. Any OpenVZ container creation took quite long time. I have not found any solution. Since i prefer KVM VMs and OpenVZ is not that important to me, i have not looked deep to find the solution. But it would be very much helpful to know the exact cause. What i am thinking is if this is a FreeNAS problem. In last couple weeks i have been doing some testing to increase my transfer speed and found FreeNAS has comparatively slow speed. It was pointed to me in other post that any FreeBSD based OS is slow. OS based on Solaris such as OpenIndiana, OmniOS has lightning fast speed as storage server. Have to give them a try.
 
Having the same issue here. I can test if need be.
pveversion
root@zwtprox1:/etc/pve/openvz# pveversion -vpve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-22-pve
proxmox-ve-2.6.32: 3.0-107
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-22-pve: 2.6.32-107
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-20
pve-firmware: 1.0-23
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1
Click to expand...

I have an NFS that can successfully house containers, templates, KVM images, and backups.
CT creation is slow, but it goes. I can see the amount used change under the storage graph.
There seems to be some iowait, so it is interacting with local storage. This is both when the CT Template is located on the NFS and on local storage.
 
Raymond Burns said:
Having the same issue here. I can test if need be.
pveversion


I have an NFS that can successfully house containers, templates, KVM images, and backups.
CT creation is slow, but it goes. I can see the amount used change under the storage graph.
There seems to be some iowait, so it is interacting with local storage. This is both when the CT Template is located on the NFS and on local storage.
Click to expand...

Have the same Problem i use Proxmox latest + freeNass NFS , Openvz very very slow creation but very KVM work great , i need Help Here ! please please
Reply
 
cloudfastservers said:
Have the same Problem i use Proxmox latest + freeNass NFS , Openvz very very slow creation but very KVM work great , i need Help Here ! please please
Reply
Click to expand...

We are seeing the exact same issue with enterprise/pvetest and no-subscription, all current kernels. At last we changed to using async to get it perform but it's not what we want. Any ideas?

SAN runs on debian squeezewith DRDB
 
sblommers said:
We are seeing the exact same issue with enterprise/pvetest and no-subscription, all current kernels. At last we changed to using async to get it perform but it's not what we want. Any ideas?

SAN runs on debian squeezewith DRDB
Click to expand...


I am seeing the same problem. Also using NFS over DRBD (debian)

async makes a huge difference, but as you say, not ideal - even with dual PSU and battery backup.
 
You must log in or register to reply here.
Top Bottom