3 ms·
Recommended system requirements for a decent oVirt installation are huge by comparison with Kimchi's. However, Kimchi is much less configurable than oVirt. So f
by phireal 10y ago
Recommended system requirements for a decent oVirt installation are huge by comparison with Kimchi's. However, Kimchi is much less configurable than oVirt. So far as I can make out, oVirt is best suited for clustered virtualization whilst Kimchi aims mainly for single server virtualization. At least, that's how I'm using it and it seems to work well. I asked our sys admin whether oVirt would work for my HP MicroSever and he said something more lightweight would be better.
- idsout 10y agoI currently manage an oVirt installation and was surprised to see almost 20GB of memory allocated on the management node before I had a single VM spun up. It's not light, but it is powerful. Makes resizing disks, setting up networks, connecting to storage domains (Fibre Channel, iSCSI, NFS, etc), migrating VMs, logging, and many other common tasks very easy to do. The latest release, 4.0 has a beautiful dashboard that gives you a quick overview of your pool of resources. Finally, every guest OS I've run has a build of an ovirt agent that reports back to the management node on its configuration (installed software, cpu/mem/io usage, ip addresses, hostname, etc).
- rwmj 10y agoI suspect that 20GB is probably down to the JBoss and/or JVM parameters which are sized for running a datacenter.