Search results

That's not the point. Failover domains are critical if you virtualize your business. You might not care what machine a VM is running on if you are just selling VMs to customers, but in a more critical environment its essential that i.e. my load-balancers or firewalls (active and backup) are...

I know, I could do it by hand and manually config every single VM I set up in the CLI. I wonder what I need Proxmox for when I have to do everything manually anyways? I just wonder with what solution other people came up that needed failover domains...

Bump :-o nobody? I simply cannot imagine nobody has used failover domains with Proxmox? :-o

Nobody? I am wondering if nobody ever tried to use that? I think thats critical when using a cluster with more than 2 hosts?! :-o

Thanks for the feedback so far. regarding the remote console, I didn't have success with two ubuntu 13.10 installations. They should both be up-to-date. I'll check that again. Regarding the OS X I'll have to ask a colleague, I don't use OSX myself... Does anybody have an opinion on my approach...

From my experience with many VMs and many VLANs I would alway use Option 2. This makes it easy to keep an eye on what VM sees which networks, and you don't have to mess with VLANs in the VMs themselves...

Hi, We are looking into Proxmox and are testing at the moment. We need a redundant/failover system for around 100 VMs to start with. These are currently running on an old Xen cluster and we think about moving to Proxmox/KVM. Our test configuration: 3 Hosts, each 24 cores and 128GB RAM...