On 09/02/2015 15:37, Chris J Arges wrote: > > Why do you need that? If you are disabling something if you are on a > > virtualized platform, then that is most of the time (and I am not saying > > always only because of things like microcode.service) wrong. > > A use-case is disabling KSM if running inside an L1 guest. But even that might not make sense if KSM is disable in L0, I think. BTW, I think Fedora has disabled KSM by default. Paolo > This would be > changed to ensure better defaults rather than work around issues. The > qemu-kvm packaging in Ubuntu enables KSM by default if you install the > package. If we are attempting to do things like nested guests, then it > may make sense to disable KSM when installing qemu-kvm in the L1 guest. > Another solution to this issue is to not enable KSM in the package and > let the user configure this when necessary. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
