I applaud the the switch from ESXi to ProxMox. Keep in mind though that by default ESXi has queuing settings put in place to keep the environment stable under most workloads. This is especially true for storage and how it handles I/O so one guest or host do not grab all available I/O.
I installed Proxmox 4.0 beta1 on three nodes and updated to latest version.
Creating a cluster on the master node went without problems.
Adding other two nodes returns an error:
root pve2:~# pvecm add 10.25.3.45
root 10.25.3.45's password:
unable to copy ssh ID
pvecm status on master node...
I installed the setup inside vMware workstation 9.0 and the whole thing runs perfectly. I am guessing it has something to do with the integrated VB virtual switch.
I don't know if anyone has tried this before but ProxMox seems to be running just fine inside Virtualbox. I connected three nodes creating a cluster and a fourth VM (inside Virtualbox) to serve as NAS for the cluster using FreeNAS. Now, all would be perfect if it wasn't for lack of network...
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.