New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Probably because it's easier to oversell OVZ and not as easy (but still possible) to oversell KVM.
If, for example a host deploys all the VMs using virtio (http://www.linux-kvm.org/page/Projects/auto-ballooning), wouldn't it have a similar effect?
If you ever wanted a custom kernel KVM would be the way to go, also it's more likely a provider will snoop your files using openvz and what @charlesA said about overselling.
Yes
Possible, but from what I understand memory for KVM is "dedicated" no matter how much the actual box is using. OVZ isn't like that, iirc.
Ballooning requites cooperation from the guest OS to function appropriately, and is easy to disable as well. Therefore even if ballooning is enabled, it's unwise to trust it if you're not the one controlling all the guests.
With OpenVZ all you're doing is setting the max amount of RAM the guest can use, which looks like available memory to the guest. Over-committing RAM is therefore easy because you don't actually need to reserve anything as you do with KVM/Xen.
As for VPSDime, I've used their VPSes as well and if I had to guess it relies on the fact that pretty much no one would actually use all 6GB of RAM. When I was actively using mine I usually only used around 1-2GB.