First, do you all know why I verbosely and solely sticked to the SLES 11 documentation?
From my other thread :
First, a summery and links to my previous posts about documentation… And my criticsm has been hard because IMO it’s especially important for recognized and recommended documentation to be accurate. Really good and comprehensive documentation is hard to come by, and when documentation is poor, I can’t think of many worse things that exist because of the effect documentation has on disseminating truths and not falsehoods.
I’ve reviewed the SLES 12 KVM documentation and find much to be desired. I have a particular beef with the documentation currently easing into the same improperly named concepts as the openSUSE community documentation (which I object to even more strenuously than the SLES 12 documentation).
My previous posted opinion about SLES 12 virtualization documentation
"New" SUSE virtualization documentation (Applies also to openSUSE) - Open Chat - openSUSE Forums
And, the following is my earlier criticism of the openSUSE community documentation. In fact, I posted enough detail that if someone were properly compensated or otherwise motivated, each item I identified could be verified and the documentation fixed.
https://forums.opensuse.org/showthread.php/514397-Where-has-official-(PDF)-documentation-gone?highlight=tsu2+virtualization
Note that there is some good stuff in the SLES 12 documentation, but because of the misinformation which is also there a student would either have to already know enough to know what to disregard or be prepared to have to unlearn/relearn a number of concepts to be able to move ahead.
Anyway, bottom line is that IMO the SLES 11 SP4 KVM documentation is <exceptionally> good and complete… And at least for now can be considered an excellent reference. Only after the User becomes well versed in that documentation, then the SLES 12 SP2 KVM documentation is an interesting read because there <are> some nuggets of really good stuff in there, too.
And I don’t think mr tsu2 is nuts or something.
@nrickert :
Your comments begin to calm me down a bit, so thanks for that.
But then, was doing “modprobe vhost-net” as root user a big death mistake, very just like trying “lsmod --help” and getting the error instead of having just “man lsmod”? Did I put the whole OS host in danger or buggy? Do I need to clean reinstall yet again!?