* Reduces overhead, in both CPU usage and memory, because of the shared kernel
* Lends itself naturally to file-based backups and snapshots
* Allows for online resizing
* Relieves the user of responsibility for kernel updates
* Is still an unproven technology in a commercial hosting environment
* Does not permit control over the kernel for guests
* May not allow resource isolation as strong as KVM's, but then Linux does have a cgroup-based scheduling option
Since neither KVM nor LXC requires a special kernel or a hypervisor beneath the host kernel, it should be straightforward to offer both, even on the same host machine, and use the same logic for allocating droplets of either type.