-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Actually this action was useful and still may be.
The problem here is that there are other virtualization solutions (virtualbox, vmware and others) who may use the same CPU support as kvm uses. At least in the past, up to and including kernel 2.6.31, it wasn't possible to run vmware when kvm modules were loaded. So the "stop" action here served as a workaround, a shorthand for "rmmod kvm-amd" or "rmmod kvm-intel" before running anything else that requires the same CPU extensions. Now with 2.6.32+ and updated vmware modules that becomes unnecessary, but I'd say let it be there for some time, when we will be sure different virtualisation solutions does not fight with each other any more. Thanks. /mjt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iJwEAQECAAYFAks702wACgkQUlPFrXTwyDjxKQQAxcb0YrzUaFYvB9LwgTsnLxE4 CKZSkr+13u+YiKa7ufdAAdRXxGNF/sixLf7Wpxu3KUQLQo+bJI8yZ9uiWGmvDcGQ 1O5sevbcfQZHfAJZZ5WTsq90euofl5whD7Wdg3zWelTk09wwa24W0xizGCl69CFa voUcU5QDDHwRt/m5qQw= =hyqV -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
