Thanks for finding the typos! I corrected the post above.
I've found IO speed to be acceptable, but I haven't put it under serious load. GlusterFS 3.3 has greatly improved performance as a VM storage backend, but it's still in beta. Hopefully the Redhat acquisition will get finished up soon...
I've been trying out containers in PVE 2.0. I had some issues migrating that has left me in a weird state. Here's what I did:
- 2-node PVE 2.0 cluster
- Created a new CT (104) on node A
- Using ubuntu 10.04 x86_64 template, with bridge networking
- Started it up, confirmed networking correct...
Ok, here's what I've done. Warning though, I use Gluster for KVM image storage, and not for openvz (yet?).
First, get the most recent stable Gluster .deb file from http://www.gluster.org/download/. I'm using 3.2 right now. 3.3 is supposed to have improved performance as VM storage, but it's...
Ok, found the solution:
Add the line:
options vers=3
to /etc/pve/storage.cfg beneath my NFS entry.
It would be nice to have NFS options available via the GUI though :p
Hello,
I've got a cluster setup that I'd like to make use of a GlusterFS cluster via NFS. However, Gluster only supports NFS version 3. It looks like the kernel on PVE 2.0 defaults to nfs4. Is there a way to get PVE to use nfs version 3? I can manually mount the volume as version 3, but I don't...
I bet this is just because of how I set my test up:
- I have VE 1.9 on two servers, in a cluster
- I created two VMs in the cluster, on which I installed VE 2.0
- I clustered the two VE 2 vms
- I create a vm on one of them, and when I went to start it, I got the error:
No Accelerator found...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.